User interfaces for location tracking

ABSTRACT

In some embodiments, an electronic device displays visual indications to a user when an electronic device is associated with a particular user account. In some embodiments, an electronic device displays notifications of a separation with a remote locator object (and/or device). In some embodiments, an electronic device utilizes a first or second locator process for locating a device or a remote locator object based on the device or remote locator object being located. In some embodiments, an electronic device facilitates finding associated components that are at one or more physical locations. In some embodiments, an electronic device facilitates display of location information of associated components that are at one or more physical locations.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.63/176,680, filed Apr. 19, 2021, and U.S. Provisional Application No.63/363,023, filed Apr. 14, 2022, the contents of which are incorporatedherein by reference in their entireties for all purposes.

FIELD OF THE DISCLOSURE

This relates generally to user interfaces associated with tracking thelocation of an electronic device or objects associated with anelectronic device

BACKGROUND OF THE DISCLOSURE

User interaction with electronic devices has increased significantly inrecent years. These devices can be devices such as computers, tabletcomputers, televisions, multimedia devices, mobile devices, and thelike.

In some circumstances, users may wish to use such devices to trackitems. Enhancing the user's interactions with the device improves theuser's experience with the device and decreases user interaction time,which is particularly important where input devices arebattery-operated.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

SUMMARY OF THE DISCLOSURE

Some embodiments described in this disclosure are directed to one ormore electronic devices that display visual indications to a user whenan electronic device is associated with a particular user account. Someembodiments described in this disclosure are directed to one or moreelectronic devices that display notifications of a separation with aremote locator object (and/or device). Some embodiments described inthis disclosure are directed to one or more electronic devices thatutilize a first or second locator process for locating a device or aremote locator object based on the device or remote locator object beinglocated. Some embodiments described in this disclosure are directed toone or more devices that facilitate finding associated components thatare at one or more physical locations. Some embodiments described inthis disclosure are directed to one or more devices that facilitatedisplay of location information of associated components that are at oneor more physical locations. The full descriptions of the embodiments areprovided in the Drawings and the Detailed Description, and it isunderstood that the Summary provided above does not limit the scope ofthe disclosure in any way.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 5I-5N provide a set of sample tactile output patterns that may beused, either individually or in combination, either as is or through oneor more transformations (e.g., modulation, amplification, truncation,etc.), to create suitable haptic feedback in various scenarios and forvarious purposes, such as those mentioned above and those described withrespect to the user interfaces and methods discussed herein.

FIGS. 6A-6LL illustrate exemplary ways of displaying visual indicationsto a user when an electronic device is associated with a particular useraccount in accordance with some embodiments of the disclosure.

FIGS. 7A-7H are flow diagrams illustrating a method 700 of displayingvisual indications to a user when an electronic device is associatedwith a particular user account in accordance with some embodiments.

FIGS. 8A-8T illustrate exemplary ways in which an electronic devicedisplays notifications of a separation with a remote locator object(and/or device) in accordance with some embodiments of the disclosure.

FIGS. 9A-9J are flow diagrams illustrating a method 900 of displayingnotifications of a separation with a remote locator object (and/ordevice) in accordance with some embodiments.

FIGS. 10A-10T illustrate exemplary ways in which an electronic deviceutilizes a first or second locator process for locating a device or aremote locator object based on the device or remote locator object beinglocated in accordance with some embodiments of the disclosure.

FIGS. 11A-11F are flow diagrams illustrating a method 1100 of utilizinga first or second locator process for locating a device or a remotelocator object based on the device or remote locator object beinglocated in accordance with some embodiments.

FIGS. 12A-12TT illustrate exemplary ways in which an electronic devicefacilitates finding associated components that are at one or morephysical locations in accordance with some embodiments of thedisclosure.

FIGS. 13A-13J are flow diagrams illustrating a method 1300 of findingassociated components that are at one or more physical locations inaccordance with some embodiments.

FIGS. 14A-14I illustrate exemplary ways in which an electronic devicefacilitates display of location information of associated componentsthat are at one or more physical locations in accordance with someembodiments of the disclosure.

FIGS. 15A-15E are flow diagrams illustrating a method 1500 offacilitating display of location information of associated componentsthat are at one or more physical locations in accordance with someembodiments of the disclosure.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices to track the location of objectsor devices and generate notifications associated with objects ordevices. There is also a need for electronic devices to indicate if theyare associated with a particular user account and/or are trackable by aparticular user account. Such techniques can reduce the cognitive burdenon a user who uses such devices and/or wishes to control their use ofsuch devices, and such technique can provide enhanced privacy orsecurity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. lA areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. lA shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. lA shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. lA and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from 110subsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 900,1100, 1300 and 1500 (FIGS. 7, 9, 11, 13 and 15). A computer-readablestorage medium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

In addition, in methods described herein where one or more steps arecontingent upon one or more conditions having been met, it should beunderstood that the described method can be repeated in multiplerepetitions so that over the course of the repetitions all of theconditions upon which steps in the method are contingent have been metin different repetitions of the method. For example, if a methodrequires performing a first step if a condition is satisfied, and asecond step if the condition is not satisfied, then a person of ordinaryskill would appreciate that the claimed steps are repeated until thecondition has been both satisfied and not satisfied, in no particularorder. Thus, a method described with one or more steps that arecontingent upon one or more conditions having been met could berewritten as a method that is repeated until each of the conditionsdescribed in the method has been met. This, however, is not required ofsystem or computer readable medium claims where the system or computerreadable medium contains instructions for performing the contingentoperations based on the satisfaction of the corresponding one or moreconditions and thus is capable of determining whether the contingencyhas or has not been satisfied without explicitly repeating steps of amethod until all of the conditions upon which steps in the method arecontingent have been met. A person having ordinary skill in the artwould also understand that, similar to a method with contingent steps, asystem or computer readable storage medium can repeat the steps of amethod as many times as are needed to ensure that all of the contingentsteps have been performed.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. lA or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

In some embodiments, electronic device 500 includes one or more tactileoutput generators, where the one or more tactile output generatorsgenerate different types of tactile output sequences, as described belowin Table 1. In some embodiments, a particular type of tactile outputsequence generated by the one or more tactile output generators of thedevice corresponds to a particular tactile output pattern. For example,a tactile output pattern specifies characteristics of a tactile output,such as the amplitude of the tactile output, the shape of a movementwaveform of the tactile output, the frequency of the tactile output,and/or the duration of the tactile output. When tactile outputs withdifferent tactile output patterns are generated by a device (e.g., viaone or more tactile output generators that move a moveable mass togenerate tactile outputs), the tactile outputs may invoke differenthaptic sensations in a user holding or touching the device. While thesensation of the user is based on the user's perception of the tactileoutput, most users will be able to identify changes in waveform,frequency, and amplitude of tactile outputs generated by the device.

More specifically, FIGS. 5I-5K provide a set of sample tactile outputpatterns that may be used, either individually or in combination, eitheras is or through one or more transformations (e.g., modulation,amplification, truncation, etc.), to create suitable haptic feedback invarious scenarios and for various purposes, such as those mentionedabove and those described with respect to the user interfaces andmethods discussed herein. This example of a palette of tactile outputsshows how a set of three waveforms and eight frequencies can be used toproduce an array of tactile output patterns. In addition to the tactileoutput patterns shown in these figures, each of these tactile outputpatterns is optionally adjusted in amplitude by changing a gain valuefor the tactile output pattern, as shown, for example for FullTap 80 Hz,FullTap 200 Hz, MiniTap 80 Hz, MiniTap 200 Hz, MicroTap 80 Hz, andMicroTap 200 Hz in FIGS. 5L-5N, which are each shown with variantshaving a gain of 1.0, 0.75, 0.5, and 0.25. As shown in FIGS. 5L-5N,changing the gain of a tactile output pattern changes the amplitude ofthe pattern without changing the frequency of the pattern or changingthe shape of the waveform. In some embodiments, changing the frequencyof a tactile output pattern also results in a lower amplitude as sometactile output generators are limited by how much force can be appliedto the moveable mass and thus higher frequency movements of the mass areconstrained to lower amplitudes to ensure that the acceleration neededto create the waveform does not require force outside of an operationalforce range of the tactile output generator (e.g., the peak amplitudesof the FullTap at 230 Hz, 270 Hz, and 300 Hz are lower than theamplitudes of the FullTap at 80 Hz, 100 Hz, 125 Nz, and 200 Hz).

FIGS. 5I-5N show tactile output patterns that have a particularwaveform. The waveform of a tactile output pattern represents thepattern of physical displacements relative to a neutral position (e.g.,Xzero) versus time that a moveable mass goes through to generate atactile output with that tactile output pattern. For example, a firstset of tactile output patterns shown in FIG. 51 (e.g., tactile outputpatterns of a “FullTap”) each have a waveform that includes anoscillation with two complete cycles (e.g., an oscillation that startsand ends in a neutral position and crosses the neutral position threetimes). A second set of tactile output patterns shown in FIG. 5J (e.g.,tactile output patterns of a “MiniTap”) each have a waveform thatincludes an oscillation that includes one complete cycle (e.g., anoscillation that starts and ends in a neutral position and crosses theneutral position one time). A third set of tactile output patterns shownin FIG. 5K (e.g., tactile output patterns of a “MicroTap”) each have awaveform that includes an oscillation that include one half of acomplete cycle (e.g., an oscillation that starts and ends in a neutralposition and does not cross the neutral position). The waveform of atactile output pattern also includes a start buffer and an end bufferthat represent the gradual speeding up and slowing down of the moveablemass at the start and at the end of the tactile output. The examplewaveforms shown in FIGS. 5I-5N include Xmin and Xmax values whichrepresent the maximum and minimum extent of movement of the moveablemass. For larger electronic devices with larger moveable masses, theremay be larger or smaller minimum and maximum extents of movement of themass. The examples shown in FIGS. 5I-5N describe movement of a mass inone dimension, however similar principles would also apply to movementof a moveable mass in two or three dimensions.

As shown in FIGS. 5I-5K, each tactile output pattern also has acorresponding characteristic frequency that affects the “pitch” of ahaptic sensation that is felt by a user from a tactile output with thatcharacteristic frequency. For a continuous tactile output, thecharacteristic frequency represents the number of cycles that arecompleted within a given period of time (e.g., cycles per second) by themoveable mass of the tactile output generator. For a discrete tactileoutput, a discrete output signal (e.g., with 0.5, 1, or 2 cycles) isgenerated, and the characteristic frequency value specifies how fast themoveable mass needs to move to generate a tactile output with thatcharacteristic frequency. As shown in FIGS. 5I-5N, for each type oftactile output (e.g., as defined by a respective waveform, such asFullTap, MiniTap, or MicroTap), a higher frequency value corresponds tofaster movement(s) by the moveable mass, and hence, in general, ashorter time to complete the tactile output (e.g., including the time tocomplete the required number of cycle(s) for the discrete tactileoutput, plus a start and an end buffer time). For example, a FullTapwith a characteristic frequency of 80 Hz takes longer to complete thanFullTap with a characteristic frequency of 100 Hz (e.g., 35.4 ms vs.28.3 ms in FIG. SI). In addition, for a given frequency, a tactileoutput with more cycles in its waveform at a respective frequency takeslonger to complete than a tactile output with fewer cycles its waveformat the same respective frequency. For example, a FullTap at 150 Hz takeslonger to complete than a MiniTap at 150 Hz (e.g., 19.4 ms vs. 12.8 ms),and a MiniTap at 150 Hz takes longer to complete than a MicroTap at 150Hz (e.g., 12.8 ms vs. 9.4 ms). However, for tactile output patterns withdifferent frequencies this rule may not apply (e.g., tactile outputswith more cycles but a higher frequency may take a shorter amount oftime to complete than tactile outputs with fewer cycles but a lowerfrequency, and vice versa). For example, at 300 Hz, a FullTap takes aslong as a MiniTap (e.g., 9.9 ms).

As shown in FIGS. 5I-5K, a tactile output pattern also has acharacteristic amplitude that affects the amount of energy that iscontained in a tactile signal, or a “strength” of a haptic sensationthat may be felt by a user through a tactile output with thatcharacteristic amplitude. In some embodiments, the characteristicamplitude of a tactile output pattern refers to an absolute ornormalized value that represents the maximum displacement of themoveable mass from a neutral position when generating the tactileoutput. In some embodiments, the characteristic amplitude of a tactileoutput pattern is adjustable, e.g., by a fixed or dynamically determinedgain factor (e.g., a value between 0 and 1), in accordance with variousconditions (e.g., customized based on user interface contexts andbehaviors) and/or preconfigured metrics (e.g., input-based metrics,and/or user-interface-based metrics). In some embodiments, aninput-based metric (e.g., an intensity-change metric or an input-speedmetric) measures a characteristic of an input (e.g., a rate of change ofa characteristic intensity of a contact in a press input or a rate ofmovement of the contact across a touch-sensitive surface) during theinput that triggers generation of a tactile output. In some embodiments,a user-interface-based metric (e.g., a speed-across-boundary metric)measures a characteristic of a user interface element (e.g., a speed ofmovement of the element across a hidden or visible boundary in a userinterface) during the user interface change that triggers generation ofthe tactile output. In some embodiments, the characteristic amplitude ofa tactile output pattern may be modulated by an “envelope” and the peaksof adjacent cycles may have different amplitudes, where one of thewaveforms shown above is further modified by multiplication by anenvelope parameter that changes over time (e.g., from 0 to 1) togradually adjust amplitude of portions of the tactile output over timeas the tactile output is being generated.

Although specific frequencies, amplitudes, and waveforms are representedin the sample tactile output patterns in FIGS. 5I-5K for illustrativepurposes, tactile output patterns with other frequencies, amplitudes,and waveforms may be used for similar purposes. For example, waveformsthat have between 0.5 to 4 cycles can be used. Other frequencies in therange of 60 Hz-400 Hz may be used as well. Table 1 below providesrepresentative examples of tactile output/haptic feedback behaviors andconfigurations, and examples of their use with respect to the userinterfaces for managing content-based tactile outputs that areillustrated and described herein.

TABLE 1 Textural Type of Tactile (continuous) or Output SequenceWaveform Discrete “Major” MiniTap at 180 Hz Discrete “Minor” MicroTap at80 Hz Textural “Major-reduced” MiniTap at 200 Hz Discrete“Minor-Reduced” MicroTap at 200 Hz Discrete

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

User Interfaces nd Associated Processes Indicating Device Status withRespect to a User Account

Users interact with electronic devices in many different manners. Insome embodiments, an electronic device is associated with a user accountand/or is trackable by the user account. The embodiments described belowprovide ways in which an electronic device displays visual indicationsto a user when an electronic device is associated with a particular useraccount, thus enhancing the user's interactions with the electronicdevice. Enhancing interactions with a device reduces the amount of timeneeded by a user to perform operations, and thus reduces the power usageof the device and increases battery life for battery-powered devices.The ability for a user account to track the location of an electronicdevice is intended to be used by users to help locate lost or stolendevices, and the visual indications provided by the embodiments hereinclearly inform users when such location tracking is possible. It isunderstood that people use devices. When a person uses a device, thatperson is optionally referred to as a user of the device.

FIGS. 6A-6LL illustrate exemplary ways of displaying visual indicationsto a user when an electronic device is associated with a particular useraccount in accordance with some embodiments of the disclosure. Theembodiments in these figures are used to illustrate the processesdescribed below, including the processes described with reference toFIGS. 7A-7H.

FIG. 6A illustrates an exemplary device 500 that includes touch screen504. In FIG. 6A, while the electronic device 500 is associated with JohnDoe's Account (indicated by “(Associated with John Doe's Account)” inFIG. 6A), the electronic device 500 is presenting a home screen userinterface 602 that includes a plurality of selectable options 424-452(e.g., such as the home screen user interface described with referenceto FIG. 4A). In some embodiments, the plurality of selectable optionsare representations of applications, which when selected, cause theelectronic device 500 to present user interfaces of an applicationassociated with the selected representation. In some embodiments, homescreen user interface 602 is presented to a user while the phone isunlocked (e.g., the electronic device 500 is not restricting user accessto the electronic device).

In some embodiments, the electronic device 500 presents a home screenuser interface after having been configured for use with a particularuser account. For example, in FIG. 6A, the electronic device ispresenting home screen user interface 602 after having been configuredwith John Doe's Account. In some embodiments, the electronic device isconfigured with a particular user account when a user providescredentials for that particular user account during a configurationprocess of the electronic device. In some embodiments, when electronicdevice 500 is configured with the particular user account, settings ofthe particular user account optionally control/command the electronicdevice in a particular manner, as will be described in more detaillater. In some embodiments, while electronic device 500 is unlocked, auser of the electronic device is optionally able to initiate a processto reset the electronic device 500.

For example, in FIG. 6B, while electronic device 500 is displaying homescreen user interface 602 and while the electronic device is associatedwith John Doe's Account, the electronic device 500 detects touch contact622 selecting selectable option 446, which corresponds to arepresentation of a Settings application of the operating system ofdevice 500. In FIG. 6C, in response to receiving the selection ofselectable option 446, the electronic device 500 presents a userinterface 606 of the Settings application. In some embodiments, when theelectronic device 500 is associated with a user account, a userinterface of the Settings application includes selectable optionsassociated with the user account. For example, because device 500 isassociated with John Doe's Account, user interface 606 includes aselectable option 608 which is selectable to access information aboutJohn Doe's Account. In some embodiments, when the electronic device 500is associated with a user account, selectable option 608 includesinformation about an email address/username associated with the useraccount (as shown in FIG. 6C). In some embodiments, when selectableoption 608 is selected, settings of the user account are able to beviewed and adjusted, such as controlling if the electronic device 500 isable to be associated with a new user account, controlling if a user ofthe user account has access to the location of the electronic device,etc. Additionally, user interface 606 includes selectable options612-620 corresponding to various other settings of the electronic device500. In some embodiments, when selectable options 612-620 are selected,settings and/or user interfaces associated with the selected item areable to be viewed and adjusted.

In FIG. 6D, while displaying the settings user interface 606, theelectronic device 500 detects touch contact 622 selecting selectableoption 612 which corresponds to General Settings of the electronicdevice 500. In FIG. 6E, in response to the electronic device 500detecting touch contact 622 selecting selectable option 612, theelectronic device 500 presents a user interface 622 corresponding togeneral device settings. User Interface 622 includes selectable option621 for viewing information about the electronic device 500, selectableoption 624 for updating the electronic device 500, selectable option 626for adjusting time settings of the electronic device, and a selectableoption 628 for resetting the electronic device. In FIG. 6F, while theelectronic device is displaying user interface 622, the electronicdevice 500 detects touch contact 622 selecting selectable option 628.

In FIG. 6G, in response to detecting selection of selectable option 627,the electronic device 500 presents a user interface 628 for resettingthe electronic device 500. User Interface 628 includes selectable option630 for resetting all settings of electronic device 500, selectableoption 632 for erasing all content and settings of electronic device500, selectable option 634 for resetting the network settings of theelectronic device 500, and a selectable option 636 for resetting thelocation and privacy settings of the electronic device 500.

In FIG. 6H, the electronic device 500 detects touch contact 622selecting selectable option 632 which corresponds to resetting theelectronic device 500 by erasing all content and settings of theelectronic device 500. In FIG. 61, in response to receiving the touchcontact 622 selecting selectable option 632, the electronic device 500begins resetting the electronic device and erasing all content andsettings of the electronic device 500. In some embodiments, whileelectronic device 500 is performing the process of resetting theelectronic device, the electronic device 500 displays a user interfacecorresponding to the reset process. For example, in FIG. 61, while theelectronic device is being reset, the electronic device displays userinterface 638 for indicating the current progress of the reset process.

In some embodiments, after the electronic device 500 has finished thereset process, the electronic device 500 enters a sleep/low power statein which the display of the device is off. For example, in FIG. 6J,after the electronic device has finished performing the reset process,as shown in FIG. 61, the electronic device enters a sleep/low power modeand the touch screen 504 is currently off (e.g., not displaying a userinterface). In some embodiments, even after resetting the electronicdevice 500, the electronic device 500 maintains its associations withthe user account that used with the electronic device prior the devicebeing reset if the association with the user account was not removedprior to the electronic device being reset. For example, as shown inFIG. 6J, after the electronic device has been reset, the device'sassociation with John Doe's account is still maintained (indicated by“(Associated with John Doe's Account)”). In FIG. 6K, while theelectronic device 500 is in a sleep/lower power mode and while theelectronic device is still associated with John Doe's account, theelectronic device 500 detects a wake command corresponding to a requestto turn on the touch screen 504. In some embodiments, the wake commandis issued to the electronic device 500 when the electronic devicedetects a touch contact 622 while the touch screen is off, as shown inFIG. 6K. In some embodiments, the wake command is issued to theelectronic device when the electronic device detects a tap/clickdirected to a power button of the electronic device while the touchscreen 504 is off.

In some embodiments, after the electronic device 500 has completed thereset process, the electronic device in a state in which a new useraccount can be associated with the electronic device (e.g., a devicesetup state)—if a user account currently associated with the electronicdevice allows, or if the electronic device is not currently associatedwith a user account. For example, in FIG. 6L, in response to theelectronic device 500 receiving the wake command, the electronic device500 displays user interface 640. As shown in FIG. 6L, user interface 640is displayed after the electronic device 500 has been reset and before auser starts a process for configuring the electronic device with a newuser account. In some embodiments, user interface 640 is optionally thefirst user interface that is displayed by the electronic device 500after the electronic device has been reset.

As shown in FIG. 6L, the user interface 640 includes a welcome message(“Hello”), an indication of how to initiate a process to beginconfiguring the electronic device (“Swipe to continue”), an indication642 indicating that the electronic device is locked to John Doe'saccount, and an indication 644 indicating that the electronic device issharing its location with John Doe's account. In some embodiments,visual indication 642 is displayed if the electronic device 500 isassociated with a respective user account and if a setting of that useraccount is preventing other user accounts from being associated with theelectronic device. In some embodiments, if the electronic device 500 isassociated with a user account, but a setting of that user account isnot preventing other accounts from being associated with the electronicdevice—or, if device 500 is not associated with a user account—thenvisual indication 642 is not included in the user interface 640. In someembodiments, if a user account (or a setting of a user account) ispreventing another account from being associated with device 500, theelectronic device 500 is unable to be associated with another useraccount until the user account is disassociated with the electronicdevice or the setting preventing another user account from beingassociated with the electronic is turned off.

In some embodiments, when the electronic device is locked to aparticular user account, user interface 640 optionally includes anindication about the particular user account to which the electronicdevice is locked (or the user associated with the user account). Forexample, in FIG. 6L, indication 642 includes a redacted email address ofthe user account to which device 500 is currently locked.

In some embodiments, visual indication 644 is displayed if theelectronic device 500 is associated with a respective user account andif a setting of that user account is causing the electronic device toshare its location with the user account. In some embodiments, if theelectronic device is associated with a user account, but a setting ofthat user account is not causing the electronic device to share itslocation with the user account--or if device 500 is not associated witha user account—then visual indication 644 is not included in the userinterface 640. In some embodiments, if a user account (or a setting of auser account) is causing the electronic device to share its locationwith the user account, a user of that user account is able to access alocation of the electronic device. Similarly, in some embodiments, ifafter an electronic device has been reset and the electronic device isnot currently associated with any user account, user interface 640 doesnot include visual indications 642, 644, as show in FIG. 6L-1.

In FIG. 6M, while displaying user interface 640 and visual indications642 and 644, the electronic device 500 detects a swipe (indicated bytouch contact 622 moving to the right on touch screen 504) correspondingto a request to initiate the process of configuring the electronicdevice 500 with a new user account. In some embodiments, if anelectronic device is unable to be configured with a new user account(because it is currently locked to another user account), the electronicdevice is not able to be configured with a new user account.

Instead, in some such embodiments, the electronic device requiresaccount credentials of the user account currently associated with theelectronic device before it allows a new user account to becomeassociated with the electronic device. For example, in FIG. 6N, inresponse to receiving the request to configure the electronic device 500with a new user account (e.g., as part of the process initiated inresponse to the input detected in FIG. 6M), the electronic device 500displays a user interface 646 requesting the credentials of John Doe'sAccount (e.g., the user account to which device 500 is currently lockedand/or with which device 500 is currently associated). In someembodiments, until the credentials of John Doe's Account are provided tothe electronic device 500, a user of the electronic device 500 is unableto complete the process for configuring device 500 with their useraccount and/or perform functionality such as accessing a home screen ofthe device, launching applications, sending/receiving messages, etc.Thus, in some such embodiments, the electronic device does not allow theelectronic device to be configured and used until the credentials ofJohn Doe's Account are provided to the electronic device. For example,in FIG. 6N, until the credentials of John Doe's Account are provided tothe electronic device 500, the electronic device does not allow the userto advance past user interface 646 and does not allow the user to accessfunctions of the electronic device, including accessing the home screen602 show in FIG. 6A.

In the example of FIG. 6N, the account credentials of John Doe's accounthave been provided by the user, and the electronic device 500 isoptionally able to complete the current configuration process andoptionally initiate a process to disassociate the user account currentlyassociated with the electronic device 500 (John Doe's Account). In someembodiments, a user can initiate a process to dissociate a currentlyassociated user account during the configuration process described aboveand from a user interface such as user interface 646 shown in FIG. 6N.In some embodiments, a user can initiate a process to dissociate acurrently associated user account from a settings application (e.g.,from user interface 606, as described with reference to FIG. 6C). Forexample, John Doe's account optionally becomes disassociated withelectronic device 500 when a user “signs out” or deletes the useraccount from the electronic device (e.g., by interacting with one ormore user interfaces displayed in response to selecting item 608 in FIG.6C). In some embodiments, after disassociating a user account from theelectronic device, a new user account optionally can be associated withthe electronic device when a user provides credentials of the new useraccount to the device 500 (e.g., signing in via a displayed userinterface in response to selecting item 608 in FIG. 6C).

For example, before displaying the lock screen user interface 648 inFIG. 60, electronic device 500 is disassociated with John Doe's Accountand associated with Johnny Appleseed's Account, in a manner similar towhat was described above. In some embodiments, if the electronic device500 is associated with a user account when a lock screen or wake screenuser interface is being displayed, the lock screen user interfaceincludes information about that user account. In some embodiments, thelock screen or wake screen user interface is the first user interfacedisplayed by device 500 in response to waking from a low or no-powerstate while device 500 is configured (e.g., while device 500 is not in adevice setup state). For example, in FIG. 60, because device 500 isassociated with Johnny Appleseed's Account and that account ispreventing other accounts from being associated with the device, thelock screen user interface includes visual indication 642 indicatingthat the electronic device is locked to Johnny Appleseed's Account.Similarly, because Johnny Appleseed's Account has access to the locationof the electronic device, the lock screen user interface includes visualindication 644 indicating that the location of the electronic device canbe accessed via the user account. In some embodiments, the visualindications displayed only include an indication of functionalityassociated with the user account (e.g., tracking the location of thedevice, device is locked, etc.), but not information about the useraccount. In some embodiments, the visual indications include both anindication of functionality associated with the user account andinformation about the account that is preventing the device from beingassociated with other user accounts (e.g., a profile photo associatedwith user account, redacted/obscured contact information associated withthe user account, and/or unmasked contact information associated withthe user account such as a full phone number, email, etc. of the user).One or more of the characteristics of indications 642 and 644 areoptionally the same as one or more of the characteristics of indications642 and 644 described with reference to FIG. 6L. Further, in someembodiments, one or more of indications 642 or 644 are displayed whetheror not device 500 is locked or unlocked (e.g., having authentication auser using biometric identification, such as fingerprint or facerecognition, for example) while displaying user interface 648.

In some embodiments, even if a user account is associated with theelectronic device when displaying a lock screen user interface, the lockscreen or wake screen user interface optionally does not include visualindications associated with the user account. For example, in FIG. 60-1,even though device 500 is associated with Johnny Appleseed's Account andthat account is preventing other user accounts from being associatedwith device 500, and that account has access to the location of theelectronic device, lock screen user interface 648 does not include anyvisual indications associated with this functionality.

In FIG. 6P, while displaying the lock screen or wake screen userinterface 648, and while device 500 is locked (e.g., before anysuccessful authentication input, such as a password, a PIN code, facialauthentication, fingerprint authentication, other biometricauthentication, etc., is provided to device 500) the electronic device500 detects a downward swipe starting from an upper-right portion oftouch screen 504 (indicated by touch contact 622). In FIG. 6Q, inresponse to receiving the downward swipe, electronic device 500 displaysuser interface 650 while device 500 remains locked. User interface 650is optionally a control center user interface that includes one or morecontrols for controlling one or more functionalities of device 500. Forexample, user interface 650 in FIG. 6Q includes toggle button 652 forturning airplane mode on or off (e.g., allows or restricts electronicdevice 500 from receiving or transmitting wireless signals), togglebutton 654 for toggling cellular data on or off (e.g., allows orrestricts electronic device 500 from using cellular data), toggle button658 for toggling Wi-Fi on or off (e.g., allows or restricts electronicdevice 500 from using Wi-Fi), and toggle button 656 for togglingBluetooth on/off (e.g., allows or restricts electronic device 500 fromusing Bluetooth). User interface 650 also includes various otherselectable controls for controlling functionality of the electronicdevice, including controls for adjusting the display brightness of thetouch screen 504, adjusting music playback volume, etc.

In the example of FIG. 6Q, toggle button 652, associated with anairplane mode of the device, is toggled off (represented by thegray-scale fill) indicating the electronic device is not in airplanemode. Toggle buttons 654-658 are toggled on indicating that theelectronic device is allowing use of Wi-Fi, Bluetooth, and cellulardata. In FIG. 6R, while toggle button 652—associated with an airplanemode of the device—is toggled off and while device 500 remains locked,the electronic receives a selection of toggle button 652 (indicated bytouch contact 622). In FIG. 6S, in response to receiving the selectionof toggle button 652, toggle 652 button toggles on. In some embodiments,the functions of the electronic that turn off in response to airplanemode toggling on are based on whether the electronic received thetoggling on input in a device locked or device unlocked state. Forexample, in FIG. 6S, because the electronic device 500 received therequest to toggle airplane mode on when the device was in a lockedstate, the electronic device restricts use of cellular data and Wi-Fi(indicated by toggle buttons 654 and 658 toggling to an off state(represented by gray-scale fill in toggle buttons 654 and 658)) whilestill allowing at least some communications via Bluetooth (representedby cross hatch fill in toggle button 656). Bluetooth communication isoptionally not able to be toggled completely off when a device isairplane mode so that functionality associated with the user accountwith which device 500 is associated can continue to function—or stateddifferently, to prevent a user of device 500 from disabling suchfunctionality while device 500 is locked. For example, when a device isunable to transmit information about a location of the electronicdirectly to the user account (e.g., with cellular or Wi-Fi signalsbecause of airplane mode being turned on), the electronic deviceoptionally utilizes Bluetooth to broadcast information about thelocation of device 500 to other electronic devices in range of theBluetooth signal, which in turn allows the other electronic devices totransmit information about the location of the electronic device to theuser account. In FIG. 6S, a user of Johnny Appleseed's Account still hasaccess to the location of the electronic device even after airplane istoggled on because the device 500 is able to transmit information aboutits location via Bluetooth, as described above. Because JohnnyAppleseed's Account still has access to the location of the electronicdevice, even while in airplane mode, user interface 650 includes anindicator 660 indicating that the location of the device 500 is beingshared with Johnny Appleseed's account. Indicator 660 optionally hascharacteristics similar to or the same as indicators 642 and 644, whichwere described above. Additionally, indicator 660 is optionallydisplayed in the same region as toggle buttons 652-656 or is displayedin a different region of user interface 650. In some embodiments, ifJohnny Appleseed's account did not have a setting for accessing thelocation of device 500 turned on (e.g., enabled), indicator 660 wouldnot be included in user interface 650. In some such embodiments,Bluetooth communication could be fully turned off from user interface650 while device 500 is locked. Alternatively, even in embodiments wherea user account does not have a setting for accessing the location ofdevice 500 turned on, Bluetooth communication is optionally not able tobe fully turned off from user interface 650 while device 500 is locked.

In some embodiments, while the electronic device is in airplane modewhile device 500 remains locked, Bluetooth remains at least partiallyactive and cannot be toggled fully off (e.g., to allow device 500 toshare location with a currently associated user account). In FIG. 6T, aselection of toggle button 656 (associated with the Bluetooth devicesetting) is detected while device 500 is locked and in airplane mode,and Bluetooth is in a “partially on” state. In FIG. 6U, in response todetecting the selection of Bluetooth toggle button 656, Bluetoothbecomes fully enabled (indicated by solid fill of toggle button 656). Insome embodiments, when Bluetooth is fully on, the device 500 is able topair/connect with other with other Bluetooth devices and utilizeBluetooth functionality with no restrictions. Additionally, becauseairplane mode remains on, the user interface 650 continues to displayindicator 660 to indicate that the location of the device is beingshared with Johnny Appleseed's account. In some embodiments, if airplanewas toggled off, the electronic device 500 would cease display ofindicator 660 in the user interface 650.

In FIG. 6V, while displaying user interface 650, the electronic device500 detects a swipe in an upward direction on touch screen 504 (asindicated by touch contact 622). In FIG. 6W, in response detecting theswipe, the electronic device ceases display of user interface 650 andre-displays lock screen user interface 648, which was described above.Device 500 in FIG. 6W is still in a locked state.

In FIG. 6X, while the electronic device is displaying lock screen userinterface 648, the electronic device 500 receives a swipe up on touchscreen 504 (indicated by touch contact 622 moving upward) to initiate aprocess to unlock device 500. In FIG. 6Y, in response to detecting theupward swipe, the electronic device 500 displays user interface 680.User interface 680 includes virtual keypad 682. Virtual keypad 682 isconfigured to accept selection of one or more keys in virtual keypad682. When the one or more key selections satisfy criteria for unlockingthe device (e.g., the keys selected correspond to the correct PIN codefor device 500), the device optionally is unlocked and presents a homescreen user interface 602, as shown in FIG. 6Z. The home screen userinterface 602 illustrated in FIG. 6Z is similar to the home screen userinterface 602 described with reference to FIG. 6B, but optionallydisplays different application and/or content based on profile andcustomization settings associated with Johnny Appleseed's Account. Whilethe electronic device 500 is described as requiring a PIN code forunlocking the device, one of skill in the art would understand thatvarious other forms of authentication, including biometricauthentication, could be utilized (e.g., facial and/or touchauthentication) for unlocking the electronic device without departingfrom the embodiments of the disclosure.

In some embodiments, while the device is displaying a home screen userinterface, a user of the electronic device is able to launch one or moreapplications. For example, in FIG. 6AA, while electronic device 500 isdisplaying home screen user interface 602, while device 500 is unlocked,and while the electronic device is associated with Johnny Appleseed'sAccount, the electronic device 500 detects touch contact 622 selectingselectable option 446, which corresponds to a representation of aSettings application.

In FIG. 6BB, in response to receiving the selection of selectable option446, the electronic device presents a user interface 606 of the Settingsapplication. In some embodiments, if the device 500 is associated with arespective user account when displaying a user interface of a settingsapplication, the user interface includes a selectable option foraccessing information about the respective user account, such asselectable option 608. As illustrated in FIG. 6BB, selectable option 608includes information about a name of a user associated with the useraccount (“Johnny Appleseed”), a profile icon associated with the useraccount, and an email address/username associated with the user account(Johnny.Appleseed@email_provider.com). In some embodiments, whenselectable option 608 is selected, settings of the user account are ableto be viewed and adjusted, such as if the electronic device is able tobe associated with a new user account, if a user of the user account hasaccess to the location of the electronic device, etc.

Additionally, user interface 606 includes selectable optionscorresponding to various settings of the electronic device 500,including selectable option 618 corresponding to managing Bluetoothsettings on the device. In FIG. 6CC, the electronic device 500 detects aselection input directed to selectable option 618 via a tap of touchcontact 622. In response to receiving the selection input, theelectronic device 500 presents a Bluetooth settings user interface 670,as shown in FIG. 6DD. Bluetooth settings user interface 670 includestoggle button 672 (currently on) for toggling Bluetooth connections onthe electronic device on/off, and a list of devices 674 currentlyconnected to device 500 via Bluetooth.

In FIG. 6EE, the electronic device detects a selection input fortoggling off toggle button 672. In 6FF, in response to receiving theselection input for toggling off toggle button 672, the electronicdevice 500 disables Bluetooth on the electronic device, and terminatesthe Bluetooth connection between device 500 and the Devices 1 and 2.Because Bluetooth connectivity was toggled off while the device wasunlocked, the device allows Bluetooth communications on the device to befully disabled—in contrast to not allowing Bluetooth communications tobe toggled fully off when device 500 was in a locked state (as describedwith reference to FIGS. 6R-6U). It is understood that the control centeruser interface 650 described with reference to FIGS. 6Q-6U couldsimilarly be accessed while device 500 is in an unlocked state, in whichcase Bluetooth communications could similarly be toggled fully off fromuser interface 650 (e.g., in response to toggling of airplane modebutton 652 or toggling of Bluetooth button 656).

FIGS. 6GG-6II illustrate exemplary ways of providing an indication to auser about functionality associated with a user account when the deviceis being powered down. In FIG. 6GG, device 500 is displaying a userinterface 676 associated with powering down device 500. User interface676 includes a background 678 and draggable user interface element 681.In the example of FIG. 6GG, powering down the electronic device 500requires user interface element 681 to be horizontally dragged tolocation 684 (or within a threshold distance of location 684).

In FIG. 6HH, the electronic device detects that touch contact 622 hasstarted dragging the user interface element 681 towards location 684. Inresponse to user interface element 681 moving towards location 684, andbecause device 500 is currently associated with a user account,indications 642 and/or 644 (as described above) begin to be displayed inuser interface 676. In some embodiments, as touch contact 622 moves thedraggable user interface element 681 closer to an ending location,indications 642 and 644 become more visibly displayed by device 500(e.g., more visible to a user of the electronic device). For example, inFIG. 611, the electronic device 500 detects further movement of userinterface element 681 towards location 684. In response to detecting thefurther movement, device 500 decreases the translucency of indications642 and/or 644 in accordance with the movement of user interface element681. In FIG. 6JJ, the electronic device 500 again detects furthermovement of user interface element 681 towards location 684. In responseto detecting the further movement, device 500 again decreases thetranslucency of indications 642 and/or 644 in accordance with themovement of user interface element 681. Thus, in some embodiments,visual indications 642 and/or 644 are more prominently displayed bydevice 500 (e.g., displayed with less transparency) as the gesture forpowering off device 500 progresses (e.g., as touch contact 622 movesuser interface element 681 to location 684).

While FIGS. 6GG-6JJ were described in the context of indications 642 and644 being visually emphasized in accordance with the movement of userinterface element 681, it would be understood to one of ordinary skillin the art that other ways exist for visually indicating functionalityassociated with a user account in user interface 676. For example,instead of visually emphasizing indications 642 and/or 644, visualindications 642 and/or 644 could instead be visually deemphasized inaccordance with the movement of user interface element 681. Further, insome embodiments, a background of user interface 676 is deemphasized asthe movement of user interface element 681 progresses while visualindications 642 and/or 644 remain displayed with a same visualcharacteristic (e.g., brightness, translucency, etc.), which results invisual indications 642 and/or 644 being displayed with more relativevisual emphasis as the movement of user interface element 681progresses. In some embodiments, visual indication 642 is displayed inuser interface 676 if the electronic device 500 is associated with arespective user account and if a setting of that user account ispreventing other user accounts from being associated with the electronicdevice. In some embodiments, if the electronic device 500 is associatedwith a user account, but a setting of that user account is notpreventing other accounts from being associated with the electronicdevice—or, if device 500 is not associated with a user account—thenvisual indication 642 is not included in the user interface 676. In someembodiments, visual indication 644 is displayed in user interface 676 ifthe electronic device 500 is associated with a respective user accountand if a setting of that user account is causing the electronic deviceto share its location with the user account. In some embodiments, if theelectronic device is associated with a user account, but a setting ofthat user account is not causing the electronic device to share itslocation with the user account—or if device 500 is not associated with auser account—then visual indication 644 is not included in the userinterface 676.

In some embodiments, when a device is in a low power mode, at leastfunctionality associated with the user account associated with thedevice remains active. For example, in FIG. 6KK, device 500 isdisplaying low power user interface 690. Device 500 is optionallydisplaying low power user interface 690 because the battery of theelectronic device is below a threshold charge level (e.g., less than 1%of the remaining battery). In some embodiments, at least somefunctionality associated with a user account that is associated with thedevice remains active while the device is in a low power mode. Forexample, in FIG. 6KK, the currently associated user account, JohnnyAppleseed's Account, continues to prevent the electronic device 500 frombeing associated with another user account and also continues to haveaccess to a location of the device. As a result, indications 642 and/or644 (previously described above) are displayed in low power userinterface 690. In some embodiments, the electronic device continues totransmit a current location of the device by utilizing a secondarybattery of the electronic device. Additionally, in some embodiments,functions of the electronic device other than functionality associatedwith locking the electronic device and tracking a location of the deviceremain usable in a low power mode, such as functions of the electronicdevice that do not require power to be drawn from the battery tofunction (e.g., NFC transactions (e.g., for mobile purchases and/ortransit transactions)). As shown in FIG. 6KK, when other functionalityof the electronic device remains available/usable while device 500 is inthe low power mode, low power user interface 690 includes indication 688indicating the functionality of the device that remains usable while thedevice is in low power mode. In some embodiments, visual indication 642is displayed in user interface 690 if the electronic device 500 isassociated with a respective user account and if a setting of that useraccount is preventing other user accounts from being associated with theelectronic device. In some embodiments, if the electronic device 500 isassociated with a user account, but a setting of that user account isnot preventing other accounts from being associated with the electronicdevice—or, if device 500 is not associated with a user account—thenvisual indication 642 is not included in the user interface 690. In someembodiments, visual indication 644 is displayed in user interface 690 ifthe electronic device 500 is associated with a respective user accountand if a setting of that user account is causing the electronic deviceto share its location with the user account. In some embodiments, if theelectronic device is associated with a user account, but a setting ofthat user account is not causing the electronic device to share itslocation with the user account—or if device 500 is not associated with auser account—then visual indication 644 is not included in the userinterface 690. In some embodiments, visual indication 688 is optionallydisplayed in user interface 690 if a setting of a user account currentlyassociated with the electronic device permits use of one or morefunctions of the electronic device while the device is in a low powermode. In some embodiments, visual indication 688 is optionally notdisplayed in the user interface 690 if a setting of the user accountcurrently associated with the electronic device does not permit use ofone or more functions of the electronic device while the device is in alow power mode.

In some embodiments, at least some functionality associated with theuser account that is associated with an electronic device remains activewhile attempting to recover access to the electronic device. Forexample, in FIG. 6LL, device 500 is displaying recovery user interface692. Device 500 is optionally displaying recovery user interface 692because an Operating System of the device is corrupted. In someembodiments, at least some functionality associated with a user accountthat is associated with the device remains active while the device isbeing recovered. For example, in FIG. 6LL, the currently associated useraccount, Johnny Appleseed's Account, continues to prevent the electronicdevice 500 from being associated with another user account and alsocontinues to have access to a location of the device. As a result,indications 642 and/or 644 (previously described above) are displayed inrecovery user interface 692. In some embodiments, the electronic devicecontinues to transmit a current location of the device and stilltransmits information about its location to the user account currentlyassociated with the electronic device by executing this functionality onone or more processors of the computing device not associated with thecorrupted operating system. It is understood that indicators 642 and 644in user interface 692 optionally have the same characteristics of theindictors 642 and 644 described with reference to FIGS. 6HH-JJ, thus areoptionally displayed and not displayed in a similar manner.

FIGS. 7A-7H are flow diagrams illustrating a method 700 of displayingvisual indications to a user when an electronic device is associatedwith a particular user account in accordance with some embodiments, suchas in FIGS. 6A-6LL. The method 700 is optionally performed at anelectronic device such as device 100, device 300, or device 500 asdescribed above with reference to FIGS. 1A-1B, 2-3, 4A-4B and 5A-5H.Some operations in method 700 are, optionally combined and/or order ofsome operations is, optionally, changed.

As described below, the method 700 provides ways to display visualindications to a user when an electronic device is associated with aparticular user account t. The method reduces the cognitive burden on auser when interacting with a user interface of the device of thedisclosure, thereby creating a more efficient human-machine interface.For battery-operated electronic devices, increasing the efficiency ofthe user's interaction with the user interface conserves power andincreases the time between battery charges.

In some embodiments, method 700 is performed at an electronic device incommunication with a display generation component and one or more inputdevices (e.g., a mobile device (e.g., a tablet, a smartphone, a mediaplayer, or a wearable device) including wireless communicationcircuitry, optionally in communication with one or more of a mouse(e.g., external), trackpad (optionally integrated or external), touchpad(optionally integrated or external), remote control device (e.g.,external), another mobile device (e.g., separate from the electronicdevice), a handheld device (e.g., external), and/or a controller (e.g.,external), etc.). In some embodiments, the display generation componentis a display integrated with the electronic device (optionally a touchscreen display), external display such as a monitor, projector,television, or a hardware component (optionally integrated or external)for projecting a user interface or causing a user interface to bevisible to one or more users, etc.

In some embodiments, the electronic device detects (702 a), via the oneor more input devices, a first input (e.g., an input such as a touchinput, a mouse input, selection of a wake/power button, and/or akeyboard input, etc.), wherein the first input is detected while theelectronic device is in a device setup state in which the device isprepared to be setup for use with a new user account (e.g., a state ofthe electronic device that optionally includes an operating system andone or more pre-installed applications, but does not includeapplication-specific user data, user configured settings, and/orpersonal user information. In some embodiments, the electronic device isin the device set-up state when it has not been configured, set-up,and/or initialized by a user. In some embodiments, the electronic deviceis in the device set-up state when the electronic device has been resetand/or erased to remove user specific data/information. In someembodiments, the first input wakes the device from an off or lower powerstate (e.g., in which the display generation component is off and/or notdisplaying content and/or displaying a screensaver or lower power userinterface)) and before starting a process for configuring the electronicdevice for use with the new user account, such as touch contact 622 andthe state of the device in FIG. 6K (e.g., before initiating a process toassociate the electronic device with (e.g., functionality defined by)the new user account)). For example, the electronic device detects thefirst input while the device is in the device setup state and before aprocess to configure the electronic device with a new user account isinitiated. In some embodiments, starting a process for configuring theelectronic device with a new user account includes first displaying auser interface for setting a particular device setting (e.g., defaultlanguage, Wi-Fi network, device password, etc.).

In some embodiments, in response to detecting the first input, theelectronic device displays (702 b), via the display generationcomponent, a user interface of the electronic device, such as userinterface 640 in FIG. 6L (e.g., a user interface that does not includeuser interface elements for accepting inputs that provide configurationinformation to the device). For example, in response to detecting thefirst input (e.g., while the device is in a device setup state andbefore starting a process to configure the electronic device with a newuser account), the electronic device displays a default user interfaceof the device setup state, such as a starting/welcome user interface. Insome embodiments, the starting user interface optionally includes one ormore selectable options, which when selected and/or interacted withcause the electronic device to initiate a process for configuring theelectronic device with a new user account. In some embodiments, when theelectronic device is displaying the starting user interface, theelectronic device is prepared to be associated with a new user accountbut has not started the process for configuring the electronic devicewith the new user account. In some embodiments, when an input isdirected to a selectable option on the starting user interface, thatinput starts the process for configuring the device with the new useraccount.

In some embodiments, in accordance with a determination that theelectronic device is currently associated with a user account that wasused with the device prior to the device being reset to the device setupstate (e.g., before the electronic device entered the device setupstate, the electronic device was associated with a user account), theuser interface includes an indication of functionality associated withthe user account that was used with the device prior to the device beingreset to the device setup state (702 c), such as user interface 640including indications 642 and 644 because device 500 is locked to andtracked by John Doe's Account (e.g., an indication of functionalityenabled, in part, by the association with a respective user account). Insome embodiments, an association between a respective user account andthe electronic device is established when a user authorizes theelectronic device to have access to the respective user account (e.g., auser provides the credentials of the respective user account to theelectronic device) and/or when a user authorizes the association betweenthe respective user account and the device. For example, the electronicdevice was previously associated with the respective user account beforethe device was placed into the current device setup state, and was notdisassociated from the device before the device was placed into thedevice setup state (e.g., via an input to reset all settings and/orerase all data on the device). In some embodiments, the associationbetween the device and the respective user account is stored on anexternal server, and therefore is not lost when the device is placedinto the device setup state. In some embodiments, the devicecommunicates with the external server before displaying the userinterface to determine whether the device is currently/alreadyassociated with a respective user account).

For example, if the electronic device is associated with a respectiveuser account (e.g., a relationship between the respective user accountand the electronic device exists), the user interface displayed inresponse to detecting the first input includes an indication offunctionality associated with that respective user account. In someembodiments, one or more setting(s) of the respective user accountcontrol one or more function(s) associated with the electronic device.In such embodiments, a setting of the respective user account optionallycontrols whether other respective user accounts can be associated withthe electronic device. For example, a setting of the respective useraccount optionally restricts other accounts (e.g., accounts other thanthe respective user account) from being associated with the electronicdevice while the device is associated with the respective user account.If a setting of the respective user account that restricts otheraccounts from being associated with the electronic device is enabled, anindication of this restriction is optionally displayed in the userinterface. Similarly, a second respective setting of the respective useraccount (e.g., different from the setting that restricts other accountsfrom being associated with the electronic device) optionally enables alocation of the electronic device to be tracked (e.g., accessible) viaone or more applications (e.g., using the respective account). If thesecond respective setting of the respective user account that allows alocation of the electronic device to be tracked is enabled, the userinterface optionally includes an indication that the location of theelectronic device is being tracked (e.g., or is accessible) via the oneor more applications. In some embodiments, the indication offunctionality associated with the respective user account includes anindication associated with one or more functionalities enabled, in part,by the respective user account. In some embodiments, the indication is avisual indication that includes a graphical and/or textualrepresentation of the functionality associated with the first account.

In some embodiments, in accordance with a determination that theelectronic device is not currently associated with a user account (e.g.,an association does not exist between a user account and the electronicdevice), the user interface does not include the indication offunctionality associated with the user account (702 d), such as userinterface 640 in FIG. 6L-1 not including indications 642 and 644. (e.g.,does not include an indication of functionality enabled by a respectiveuser account). In some embodiments, an association does not existbetween a respective user account and the electronic device because auser did not authorize the electronic device to obtain access to arespective user account (e.g., did not provide the credentials of therespective user account to the electronic device) and/or when a user hasrevoked an authorization allowing the electronic device to have accessto the respective user account. For example, the electronic device waspreviously associated with the respective user account and theelectronic device before the device was put in the current device setupstate (e.g., via an input to reset all settings and/or erase all data onthe device), and was disassociated from the device before the device wasplaced in the device setup state (e.g., via input to reset all settingsand/or erase all data on the device). In some embodiments, theelectronic device communicates with an external server before displayingthe user interface to determine if a device is not associated with auser account.). For example, because the electronic device is notassociated with a respective user account, the electronic device can beassociated with any respective user account, and thus, the userinterface does not include an indication that the electronic isrestricting which accounts can be associated with the electronic device.Similarly, because the electronic device is not associated with arespective user account, the location of the electronic device is nottracked (e.g., accessible) via one or more application, and thus, anindication associated with the tracking of a location of the electronicdevice is not displayed in the user interface. In some embodiments, theelectronic device can only be associated with a single user account at agiven moment in time.

The above-described manner of displaying a user interface with anindication of account functionality when an electronic device isassociated with a particular account and not displaying the userinterface with the indication of account functionality when theelectronic device is not associated with the first account providesenhanced security by informing a user if the electronic device isassociated with a respective user account, even in situations in whichsuch an association is generally missing, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient, which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, in accordance with the determination that theelectronic device is currently associated with the user account (704 a)(e.g., if the electronic device was associated with a user accountbefore being reset and/or being placed in the device setup state, andthe association with that user account still exists), in accordance witha determination that the user account corresponds to a first useraccount, the user interface includes an indication of the first useraccount (704 b), such as indication 652 in FIG. 6L including a portionof John Doe's email address (john****@***.com). For example, if thedevice is in a device setup state and associated with the first useraccount when the user interface is displayed, the user interfaceincludes an indication of the user account currently associated with theelectronic device (e.g., the first user account). In some embodiments,the indication of the first user account optionally includes an avatarassociated with the first user account (e.g., a profile photo),redacted/obscured contact information associated with the first useraccount (e.g., a redacted email, phone number, name of a user associatedwith the first user account), information about the association betweenthe electronic device and the first user account (e.g., a date/time whenthe user account become associated with the electronic device, how longthe first user account has been associated with the first user account),etc.). In some embodiments, the indication of the association with thefirst user account is selectable to contact the user associated with thefirst user account, without displaying the complete contact informationof the user (e.g., the complete phone number and/or email of the user).In some embodiments, the indication of the first user account isselectable to view a message from the user of the first user account(e.g., a message indicating that this electronic is lost/stolen and/or amessage indicating a way of contacting the user (e.g., current owner) ofthe electronic device). In some embodiments, if the first user accountis associated with a business, the indication of the first user accountincludes a logo, contact information, address or other information aboutthe business associated with the first user account.

In some embodiments, in accordance with the determination that the useraccount corresponds to a second user account, different from the firstaccount, the user interface includes an indication of the second useraccount (704 c), such as indicator 642 in FIG. 6L including informationabout a different email address if device 500 were associated with auser account other than John Doe's account. For example, if the deviceis in a device setup state and associated with the second user accountwhen the user interface is displayed, the user interface includes anindication of the user account currently associated with the electronicdevice (e.g., the second user account). In some embodiments, theindication of the second user account optionally includes an avatarassociated with the second user account (e.g., a profile photo),redacted/obscured contact information associated with the second useraccount (e.g., a redacted email, phone number, name of a user associatedwith the second user account), information about the association betweenthe electronic device and the second user account (e.g., a date/timewhen the second user account become associated with the electronicdevice, how long the second user account has been associated with thefirst user account), etc.). In some embodiments, the indication of theassociation with the second user account is selectable to contact theuser associated with the second user account, without displaying thecomplete contact information of the user (e.g., the complete phonenumber and/or email of the user). In some embodiments, the indication ofthe second user account is selectable to view a message from the user ofthe second user account (e.g., a message indicating that this electronicis lost/stolen and/or a message indicating a way of contacting the user(e.g., current owner) of the electronic device). In some embodiments, ifthe second user account is associated with a business, the indication ofthe second user account includes a logo, contact information, address orother information about the business associated with the first useraccount.

The above-described manner of displaying a user interface that includesan indication of a respective user account when the electronic device isassociated with a respective user account provides enhanced security byinforming a (e.g., unauthorized) user that a user account is currentlyassociated with the electronic device, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by avoiding an unauthorized user from proceeding withuse or setup of the device), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, the electronic device displays (706 a), via thedisplay generation component, a lock screen user interface, such as lockscreen user interface 648 in FIG. 60 (e.g., a user interface that isdisplayed while the phone is locked (e.g., user access to the electronicis being restricted), and requires user authentication (e.g., facialauthentication, fingerprint authentication, other biometricauthentication, password authentication, etc.) before moving away fromthe lock screen user interface).

In some embodiments, in accordance with a determination that theelectronic device is currently associated with a respective useraccount, the lock screen user interface includes an indication offunctionality associated with the respective user account (706 b), suchas lock screen user interface 648 including indications 642 and 644because device 500 is currently locked to and tracked by JohnnyAppleseed's Account. For example, if the electronic device is displayinga lock screen user interface while the electronic device is associatedwith a respective user account, the lock screen user interface includesan indication of functionality associated with the first user account.In some embodiments, the respective user account corresponds to a useraccount that was associated with the electronic device before the devicewas reset if the electronic device is currently in a device setup stateand is associated with a user account. In some embodiments, therespective user account corresponds to a new or current user account(e.g., a user account different than the account that was associatedwith the electronic device prior to the electronic device being reset tothe device setup state) if the lock screen user interface is beingdisplayed after the device has been setup with the new account (e.g.,whether or not the device has been reset to the device setup state). Insome embodiments, the indication of functionality includes an indicationthat the respective user account is preventing another user account(e.g., an account different from the respective user account) from beingassociated with the electronic device if the respective user account ispreventing the another user account from being associated with theelectronic device until the respective user account is disassociatedwith the electronic device. In some embodiments, the indication offunctionality includes an indication that the location of the electronicis accessible by a user of the respective user account if the respectiveuser account has access to the location of the electronic device. Insome embodiments, the indication of functionality associated with arespective user account is not included in the lock screen userinterface if the electronic device is not associated with a user accountwhen the lock screen user interface is displayed.

The above-described manner of including an indication of functionalityassociated with a respective user account when the electronic device isassociated with the respective user account provides enhanced securityby informing a (e.g., unauthorized) user of the electronic offunctionality enabled on the electronic device while in a locked state,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient, which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the electronic device displays (708 a), via thedisplay generation component, a respective user interface (e.g., adevice user interface such as an account configuration user interface,an account login user interface, a purchasing user interface, a settingsuser interface, a low power user interface, a recovery mode userinterface, etc.), wherein in accordance with the determination that theelectronic device is currently associated with a respective useraccount, the respective user interface includes an indication of therespective user account, such as user interface 640 in FIG. 6M, lockscreen user interface 648 in FIG. 6O, user interface 650 in FIG. 6S,user interface 676 in FIGS. 6HH-6JJ, user interface 690 in FIG. 6KK, anduser interface 692 in FIG. 6LL including information (e.g., redactedname/email) about the user account currently associated with device 500(e.g., that is preventing the electronic device from being associatedwith another user account).

For example, if the electronic device is associated with a respectiveuser account when a user interface of the electronic device isdisplayed, the user interface includes an indication of the respectiveuser account currently associated with the electronic device. Therespective user interface optionally corresponds to a user interfacethat is displayed while the electronic device in a device setup state orwhen the electronic device is not in a device setup state. In someembodiments, the indication of the respective user account optionallyincludes an avatar associated with the respective user account (e.g., aprofile photo), redacted/obscured contact information associated withthe respective user account (e.g., a redacted email, phone number, nameof a user associated with the respective user account), informationabout the association between the electronic device and the respectiveuser account (e.g., a date/time when the respective user account becomeassociated with the electronic device, how long the respective useraccount has been associated with the first user account), etc.). In someembodiments, the indication of the respective user account is selectableto contact the user of the respective user account, without displayingthe complete contact information of the user (e.g., the complete phonenumber and/or email of the user). In some embodiments, the indication ofrespective user account is selectable to view a message from the user ofthe first user account (e.g., a message indicating that this electronicis lost/stolen and/or a message indicating a way of contacting the user(e.g., current owner) of the electronic device). In some embodiments, ifthe respective user account is associated with a business, theindication of the respective user account includes a logo, contactinformation, address or other information about the business associatedwith the first user account. In some embodiments, based on whether theelectronic device is displaying the respective user interface while theelectronic in a device setup state, the indication of the respectiveuser account optionally includes more, less, or different informationabout the respective user account with which it is currently associatedas compared to when the electronic device is not in a setup state. Insome embodiments, the respective user account is a user account that theelectronic device was associated with before the device was reset if therespective user interface is being displayed while the electronic deviceis in a device setup state. In some embodiments, the respective useraccount is a user account that the electronic device was associated withduring the device setup state (e.g., a current user account) and/oranother device configuration process.

The above-described manner of displaying an indication of a respectiveuser account in a user interface, regardless of whether the device is oris not in a device setup state provides enhanced security by informing a(e.g., unauthorized) user about a user account already associated withthe electronic device, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the electronic device displays (710 a), via thedisplay generation component, a second user interface, different fromthe user interface, associated with a low power mode of the electronicdevice, such as low power user interface 690 in FIG. 6KK (e.g., a userinterface that is displayed when a battery of the electronic device isbelow a threshold charge level (e.g., 1%, 2%, 5%, 10%, 20% remainingbattery)). In some embodiments, the electronic device displays thesecond user interface when only a portion of the operating system of theelectronic device is able to run due to insufficient charge of thebattery. In some embodiments, the second user interface is displayedwhen a input is received to display a third user interface but is notavailable to be displayed because the battery of the electronic deviceis below a threshold amount of charge. In some embodiments, theelectronic device automatically ceases display of a prior user interface(e.g., a home screen user interface, such as described with reference toFIG. 4A), and displays the second user interface, in response to thebattery of the electronic device falling below the threshold chargelevel. In some embodiments, the second user interface includes a visualindication that indicates that the battery of the electronic devicerequires charging.

In some embodiments, in accordance with the determination that theelectronic device is currently associated with a respective useraccount, the second user interface includes the indication offunctionality associated with the user account (710 b), such as userinterface 690 including indications 642 and 644 because device 500 iscurrently associated with Johnny Appleseed's Account. For example, whilethe electronic device is displaying the second (e.g., low power) userinterface, the second user interface includes an indication offunctionality associated with a respective user account if theelectronic device is currently associated with the respective useraccount (e.g., an indication of functionality similar to the indicationof functionality included in the above mentioned respective userinterface). In some embodiments, the indication of functionalityincludes an indication of the functionality associated with the useraccount that remains active while the device is in the low power mode.For example, functionality of the respective user account that does notrequire power to be drawn from the battery (e.g., NFC transactions)and/or functionality of the respective user account that remains activeeven when the battery is below a threshold amount of charge (e.g.,functionality that operates during the power reserve mode or via use ofa secondary battery). In some embodiments, the electronic devicesupports mobile purchases and transit related transactions via NFCtransactions, thus in some embodiments, the indication of functionalityincludes an indication that mobile purchases and/or transit transactionsare available while the device is in a low power mode. In someembodiments, the respective user account prevents another user accountfrom being associated with the electronic device (e.g., while in the lowpower mode). In some such embodiments, the indication of functionalityincludes an indication that the electronic device cannot be associatedwith another user account. In some embodiments, the location of theelectronic device is accessible by the respective user account while theelectronic device is in low power mode. In some such embodiments, theindication of functionality includes an indication that the location ofthe electronic device is accessible by the respective user account. Insome embodiments, the respective user account corresponds to a useraccount that was associated with the electronic device before the devicewas reset if the electronic device is currently in a device setup stateand is associated with a respective user account. In some embodiments,the respective user account corresponds to a current or new user account(e.g., a user account different than the account that was associatedwith the electronic device prior to the electronic device being reset tothe device setup state) if the second user (e.g., low power) interfaceis being displayed after the device has been setup with the current ornew account.

In some embodiments, in accordance with the determination that theelectronic device is not currently associated with a respective useraccount, the second user interface does not include the indication offunctionality associated with the respective user account (710 c), suchas low power user interface 690 not including indications 642 and 644 ifdevice 500 were not currently associated with a user account. Forexample, if the second user interface (e.g., a low power user interface)is being displayed while the electronic device is not associated with arespective user account, the low power user interface is not displayedwith an indication of functionality associated with the respective useraccount. The above-described manner of displaying an indication offunctionality associated with a respective user account while the deviceis displaying a low power user interface and associated with arespective user account provides enhanced security by informing a userof functionality enabled on the electronic device, even while theelectronic device is in a low power mode, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient, which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, the electronic device displays (712 a), via thedisplay generation component, a second user interface, different fromthe user interface, associated with a process for recovering access tothe electronic device, such as recovery user interface 692 in FIG. 6LL(e.g., a user interface that is displayed when performing and/orinitiating a process to recover/restore access to the electronic devicedue to, for example, a corrupted operating system state on the device).In some embodiments, the second user interface includes a visualindication that indicates that the electronic device needs to beconnected to another electronic device (e.g., via USB to a computer) toproceed with recovery of the electronic device.

In some embodiments, in accordance with a determination that theelectronic device is currently associated with a respective useraccount, the second user interface includes an indication offunctionality associated with a respective user account (712 b), such asincluding indications 642 and 644 in the recovery user interface 692, inFIG. 6LL, because electronic device 500 is currently associated withJohnny Appleseed's Account. For example, while the electronic device isdisplaying the second (e.g., recovery) user interface, the second userinterface includes an indication of functionality associated with arespective user account if the electronic device is currently associatedwith the respective user account (e.g., an indication of functionalitysimilar to the indication of functionality included in the abovementioned respective user interface). In some embodiments, theindication of functionality includes an indication of the functionalityassociated with the respective user account that remains active whilethe device is initiating and/or performing a process to recover/restoreaccess to the electronic device. For example, while the electronicdevice is attempting to recover access to the electronic device, therespective user account prevents another user account from beingassociated with the electronic device. In some such embodiments, theindication of functionality includes an indication that the electronicdevice cannot be associated with another user account. In someembodiments, the location of the electronic device is accessible by therespective user account while the electronic device is being recovered.In some such embodiments, the indication of functionality includes anindication that the location of the electronic device is accessible bythe respective user account. In some embodiments, the respective useraccount corresponds to a user account that was associated with theelectronic device before the device was reset if the electronic deviceis currently in a device setup state and is associated with a respectiveuser account. In some embodiments, the respective user accountcorresponds to a current or new user account (e.g., a user accountdifferent than the account that was associated with the electronicdevice prior to the electronic device being reset to the device setupstate) if the second (e.g., recovery) user interface is being displayedafter the device has been setup with the current or new account.

In some embodiments, in accordance with a determination that theelectronic device is not currently associated with the respective useraccount, the second user interface does not include the indication offunctionality associated with the respective user account (712 c), suchas recovery user interface 692, in FIG. 6LL, not including indications642 and 644 if the device 500 were not associated with any user account.For example, if the second user interface (e.g., recovery userinterface) is being displayed while the electronic device is notassociated with a respective user account, the recovery user interfaceis not displayed with an indication of functionality associated with therespective user account.

The above-described manner of displaying an indication of functionalityassociated with a user account while the device is associated withrecovering/restoring access to the electronic device provides enhancedsecurity by informing a user of functionality enabled on the electronicdevice via the user account, even while the electronic device is beingrecovered, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient, which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the electronic device displays (714 a), via thedisplay generation component, a second user interface, different fromthe user interface, for powering down the electronic device, such asuser interface 676 in FIGS. 6GG-6JJ (e.g., a user interface configuredto initiate a process to power down the electronic device). In someembodiments, while displaying the second user interface, the electronicdevice detects (714 b), via the one or more input devices, a secondinput including a gesture associated with powering down the electronicdevice, such as the touch contact 622 moving draggable user interfaceelement 681 in FIG. 6HH-6JJ (e.g., detecting a contact from a finger ofa user moving in a particular manner (e.g., from a starting location toan ending location) to power down the electronic device). For example,the second user interface optionally includes a user interface elementthat must be moved from a first location to a second location (e.g.,horizontally) to power down the electronic device. The gestureoptionally includes a touchdown of the contact on the user interfaceelement at the first location, and movement of the contact from thefirst location to the second location.

In some embodiments, while detecting the second input (714 c) (e.g.,while detecting the finger of the user performing the gesture to powerdown the electronic device), in accordance with the determination thatthe electronic device is currently associated with a respective useraccount, the electronic device displays (714 d), in the second userinterface, the indication of functionality associated with therespective user account, such as user interface 676 includingindications 642 and 644 when touch contact 622 moves draggable userinterface element 681. For example, while the electronic device isdisplaying the second (e.g., powering down) user interface, the seconduser interface includes an indication of functionality associated with arespective user account if the electronic device is currently associatedwith the respective user account (e.g., an indication of functionalitysimilar to the indication of functionality included in the abovementioned respective user interface). In some embodiments, theindication of functionality includes an indication of the functionalityassociated with the user account that remains active when the device isoff. For example, functionality of the respective user account that doesnot require power to be drawn from the battery (e.g., NFC transactions)and/or functionality of the respective user account that remains activeeven when the electronic device is off (e.g., functionality that drawspower from the battery while the device is off or draws power from asecondary battery when the device is off). In some embodiments, theelectronic device supports mobile purchases and transit relatedtransactions via NFC transactions, thus in some embodiments, theindication of functionality includes an indication that mobile purchasesand/or transit transactions are available while the device is off. Insome embodiments, the respective user account prevents another useraccount from being associated with the electronic device (e.g., whilethe device is off). In some such embodiments, the indication offunctionality includes an indication that the electronic device cannotbe associated with another user account. In some embodiments, thelocation of the electronic device is accessible by the respective useraccount while the electronic device is off. In some such embodiments,the indication of functionality includes an indication that the locationof the electronic device is accessible by the respective user accountwhile the device is off. In some embodiments, the respective useraccount corresponds to a user account that was associated with theelectronic device before the device was reset if the electronic deviceis currently in a device setup state and is associated with a respectiveuser account. In some embodiments, the respective user accountcorresponds to a current or new user account (e.g., a user accountdifferent than the account that was associated with the electronicdevice prior to the electronic device being reset to the device setupstate) if the second user (e.g., low power) interface is being displayedafter the device has been setup with the current or new account.

In some embodiments, in accordance with the determination that theelectronic device is not currently associated with the respective useraccount, the electronic device forgoes (714 e) displaying, in the seconduser interface, the indication of functionality associated with therespective user account, such as not displaying indications 642 and 644in FIG. 6HH if no user account is associated with device 500. Forexample, if the second user interface (e.g., powering down userinterface) is being displayed while the electronic device is notassociated with a respective user account, the powering down userinterface is not displayed with an indication of functionalityassociated with the respective user account. The above-described mannerof displaying an indication of functionality associated with a useraccount as a user is performing a gesture to power down the electronicdevice provides enhanced security by informing a user of functionalityenabled on the electronic device via the user account, even after theelectronic device is off, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient,which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, while detecting the gesture associated withpowering down the electronic device, the electronic device visuallydeemphasizes (716 a) the indication of functionality associated with theuser account in accordance with progression of the gesture associatedwith powering down the electronic device, such as device 500 visuallyemphasizing indications 642 and 644 as touch contact 622 drags draggableuser interface element 681 in FIGS. 6HH-6JJ. For example, while a useris performing the gesture for powering down the electronic device, theindication of functionality fades out (e.g., deemphasizes gradually,such as by decreasing brightness, increasing translucency, etc.) as thegesture for powering down the electronic device advances. As the gesturefor powering off the electronic device concludes (e.g., criteria forpowering down the electronic device is satisfied, such as the contactreaching the second location in the user interface for powering down thedevice), the indication of functionality associated with the useraccount is optionally fully obscured or not displayed (e.g.,unobservable to a user of the electronic device). In some embodiments,the moment at which the gesture for powering down the electronic deviceis initially detected corresponds to the moment when the indication offunctionality is the most (e.g., visually) prominent. Theabove-described manner of visually deemphasizing the indication offunctionality as a gesture for powering the electronic device advancesprovides an efficient way of indicating functionality of a respectiveuser account that will be available even after powering down theelectronic device, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, while detecting the gesture associated withpowering down the electronic device, the electronic device visuallyemphasizes (718 a) the indication of functionality associated with theuser account in accordance with progression of the gesture associatedwith powering down the electronic device, such as the displaycharacteristics of indications 642 and 644 in FIGS. 6HH-6JJ. Forexample, while a user is performing a gesture for powering down theelectronic device, the indication of functionality becomes more visuallyprominent (e.g., visually emphasized, such as by increasing brightness,increasing translucency, etc.) as the gesture progresses/advances. Insome embodiments, the moment at which the gesture for powering off theelectronic concludes and subsequently causes the electronic device topower down, the indication of functionality is at its highest level ofvisual prominence (e.g., highest level of visibility). In someembodiments, the moment at which the gesture for powering off theelectronic is detected and subsequently initiates the process forpowering down the electronic device, the indication of functionality isat its lowest level of visual prominence (e.g., fully obscured or notdisplayed).

The above-described manner of visually emphasizing the indication offunctionality as a gesture for powering the electronic device advancesprovides an efficient way of indicating functionality of a user accountthat will be available even after powering down the electronic device,without the need to consume display resources to display the indicationuntil power-down is closer to be achieved, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient, which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, visually emphasizing the indication offunctionality associated with the user account in accordance with theprogression of the gesture includes maintaining a visual characteristicof the indication of functionality associated with the user accountwhile visually deemphasizing a remainder of the second user interface inaccordance with the progression of the gesture associated with poweringdown the electronic device (720 a), such if in FIGS. 6HH-6JJ the visualindications remained at a same display characteristic as draggable userinterface element 681 moves and the rest of user interface 676 fadesout. For example, while a user is performing a gesture for powering downthe electronic device, the indication of functionality remains displayedwith a same visual characteristic (e.g., same level of brightness, samelevel of translucency, etc.) while other portions of the second userinterface are visually deemphasized (e.g., fade away, reducedbrightness, increased translucency) as the gesture progresses/advances.

The above-described manner of maintaining a visual characteristic ofindication of functionality associated with a respective user account asother portions of the second user interface are visually deemphasized inaccordance with the progression of the gesture provides an efficient wayof indicating functionality of a user account that will be availableeven after powering down the electronic device, without the need toconsume increased display resources to make the indication visible asthe gesture proceeds, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, visually emphasizing the indication offunctionality associated with the user account in accordance with theprogression of the gesture includes increasing a visual characteristicof the indication of functionality associated with the user account inaccordance with the progression of the gesture associated with poweringdown the electronic device (722 a), such as the display characteristicsof indications 642 and 644 in FIGS. 6HH-6JJ. For example, while a useris performing a gesture for powering down the electronic device, acharacteristic associated with the display of the indication offunctionality (e.g., gradually) increases as the gestureprogresses/advances. In some embodiments the brightness level, opacitylevel and/or visibility level of the indication of functionality (e.g.,gradually) increases in accordance with the progression of the gesturefor powering down the electronic device.

The above-described manner of increasing a visual characteristicassociated with the indication of functionality as the gestureprogresses/advances provides an efficient way of indicatingfunctionality of a respective user account that will be available evenafter powering down the electronic device, without the need to consumedisplay resources to display the indication until power-down is closerto be achieved, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, while displaying, via the display generationcomponent, a second user interface (724 a), in accordance with thedetermination that the electronic device is currently associated with arespective user account (724 b) (e.g., if the electronic device wasassociated with a respective user account before being reset to thedevice setup state and that association still exists while in the devicesetup state or if the electronic device is associated with a currentuser account or becomes associated with a new user account during thedevice setup state), in accordance with a determination that theelectronic device is in a mode that restricts the electronic device fromreceiving or transmitting wireless signals (724 b), the electronicdevice displays (724 c), in the second user interface, an indication offunctionality associated with the user account, such as, in FIG. 6R,displaying indicator 660 in user interface 650 because airplane mode wastoggled on in FIG. 6S. For example, if the electronic device iscurrently in a (e.g., airplane) mode that is restricting the electronicdevice from receiving messages, phone calls, and/or other features ofthe electronic device over a cellular network, the second user interfaceincludes an indication of functionality associated with the respectiveuser account. In some embodiments, if the electronic device is notcurrently in a mode which is restricting the electronic device fromreceiving messages, phone calls, and/or other features of the electronicover a cellular network, the second user interface does not include anindication of functionality associated with the respective user account.

In some embodiments, the indication of functionality includes anindication of the functionality associated with the user account thatremains active while the device is restricting the transmission and/orreceiving of wireless signals (e.g., via a cellular network). Forexample, functionality of the respective user account that continues tooperate even if a connection to a cellular network cannot be establishedand/or functionality of the respective user account that remains activewhile the electronic device is restricting the transmission/receiving ofwireless signals (e.g., via a cellular network) (e.g., functionalitythat operates regardless of the mode of the electronic device). In someembodiments, the electronic device supports mobile purchases and transitrelated transactions via NFC transactions, thus in some embodiments, theindication of functionality includes an indication that mobile purchasesand/or transit transactions are available while the device is unable toreceive and/or transmit wireless signals (e.g., via a cellular network).In some embodiments, the respective user account prevents another useraccount from being associated with the electronic device (e.g., whilethe device is unable to receive and/or transmit wireless signals (e.g.,via a cellular network)). In some such embodiments, the indication offunctionality includes an indication that the electronic device cannotbe associated with another user account. In some embodiments, thelocation of the electronic device is accessible by the respective useraccount while the electronic device is unable to receive and/or transmitwireless signals (e.g., via a cellular network). In some suchembodiments, the indication of functionality includes an indication thatthe location of the electronic device is accessible by the respectiveuser account while the device is unable to receive and/or transmitwireless signals (e.g., via a cellular network). In some embodiments,the respective user account corresponds to a respective user accountthat was associated with the electronic device before the device wasreset if the electronic device is currently in a device setup state andis associated with a respective user account. In some embodiments, therespective user account corresponds to a new user account (e.g., a useraccount different than the account that was associated with theelectronic device prior to the electronic device being reset to thedevice setup state) if the second user interface is being displayedafter the device has been setup with the new account.

The above-described manner of displaying an indication of functionalityassociated with the electronic while the electronic device is in a modethat is restricting the transmission and receiving of wireless signals(e.g., via a cellular network) provides an efficient way of indicatingfunctionality of a user account that is available, even while theelectronic device has a portion of signal reception/transmissionfunctionality unavailable, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient,which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the second user interface is a user interface thatincludes one or more selectable options that are selectable to controlone or more functionalities of the electronic device (726 a), such asuser interface 650 including toggle buttons 652-658. For example, thesecond user interface includes one or more selectable options to controlfunctionality of the electronic device, including, but not limited to,selectable options to control whether the electronic device is able toreceive or transmit wireless signals (e.g., via a cellular network),such as a control to enable or disable the above-described mode of theelectronic device, to control whether the electronic device is able toreceive/transmit Wi-Fi signals, to control whether the electronic deviceis able to receive/transmit cellular signals, and/or to control whetherthe electronic device is able to receive/transmit Bluetooth signals. Insome embodiments, the one or more selectable options are displayed in afirst region of the second user interface and the indication offunctionality associated with the respective user account is located ina second region of the second user interface, different from the firstregion (e.g., above the first region). In some embodiments, when arespective selectable option is selected, the state of the electronicdevice toggles between the on/off states, unless the switching of stateswould cause the electronic device to disable functionality associatedwith the respective user account.

The above-described manner of displaying the indication of functionalityassociated with the user account provides an efficient way of indicatingfunctionality of a user account that is available, even if the or moreselectable option were to be selected by a user, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient, which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, the electronic device displays (728 a), via thedisplay generation component, a respective user interface, such as userinterface 640 in FIG. 6M, lock screen user interface 648 in FIG. 60,user interface 650 in FIG. 6S, user interface 676 in FIGS. 6HH-6JJ, userinterface 690 in FIG. 6KK, and user interface 692 in FIG. 6LL (e.g., auser interface that is displayed while the electronic is/is not in thedevice setup state, such as an account configuration user interface, anaccount login user interface, a purchasing user interface, a settingsuser interface, a low power user interface, a recovery mode userinterface, etc.)). In some embodiments, in accordance with adetermination that the electronic device is currently associated with arespective user account (e.g., if an association with a respective useraccount exists while the electronic device is/is not in the device setupstate) (728 b), in accordance with a determination that a location ofthe electronic device is accessible to the respective user account, theindication of functionality includes an indication indicating that thelocation of the electronic device is accessible to the respective useraccount (728 c), such as indicator 644 in the above mentioned userinterface including textual information indicating the device's locationis accessible by the user account currently associated with the device500. For example, if the electronic device is associated with arespective user account that has access to location information of theelectronic device, the user interface includes an indication indicatingthat the location of the electronic device is accessible by therespective user account. The respective user interface optionallycorresponds to a user interface that is displayed while the electronicdevice in a device setup state or when the electronic device is not in adevice setup state. In some embodiments, when a respective user accounthas access to location information about the electronic device, a useris able to initiate a process to find the electronic device (e.g., aswill be discussed with reference to methods 1100 and/or 1300). In someembodiments, the electronic device shares its location with anotherelectronic device (e.g., that is within a threshold distance), which inturn, communicates directly or indirectly a location of the electronicdevice to an application associated with the respective user account.

In some embodiments, in accordance with a determination that thelocation of the electronic device is not accessible to the respectiveuser account, the indication of functionality does not include anindication indicating that the location of the electronic device isaccessible to the respective user account (728 d), such as the abovementioned user interface not including indicator 644 if a user accountis not currently associated with device 500. For example, if arespective user account does not have access to location information ofthe electronic device, the user interface does not include an indicationindicating that the location of the electronic device is accessible bythe respective user account.

The above-described manner of displaying an indication that a useraccount has access to location information about the electronic devicein a user interface, regardless of whether the device is or is not in adevice setup state, provides enhanced security by informing a (e.g.,unauthorized) user about a user account that access to the location ofthe electronic device, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the electronic device receives (730 a), via the oneor more input devices, a second input corresponding to a request toenable a mode that restricts the electronic device from receiving ortransmitting wireless signals, such as device 500 receiving a request totoggle button 652 corresponding to airplane on via touch contact 622(e.g., a mode restricting the electronic device from receiving messages,phone calls, and/or other features of the electronic device over acellular network). For example, the second input is optionally selectionof an on/off toggle for enabling the mode from a control center userinterface, such as previously described. In some embodiments, inresponse to receiving the second input, in accordance with adetermination that one or more criteria are satisfied (e.g., the deviceis currently locked, and has not been unlocked via biometric or otherauthentication), the electronic device restricts (730 b) the electronicdevice from receiving or transmitting wireless signals withoutpreventing the respective user account from having access to thelocation of the electronic device, such as, in FIG. 6S, while airplanemode is toggled off, indicator 660 indicates the location of the deviceis still accessible by the currently associated user account. It isunderstood that the technology via which the respective user account isable to access the location of the electronic device is intended to beused for lost and stolen device tracking, and clearly inform users ofthe electronic device when such access is occurring or possible. Forexample, if the electronic device is locked when the request to restrictthe electronic device from receiving/transmitting of wireless signals isreceived, the electronic device disables some types of wireless signalsthat do not prevent the respective user account from having access to alocation of the electronic device. In some embodiments, a user interfaceincludes selectable options for toggling on/off one or more settings ofthe electronic (e.g., such as toggling settings as cellular, Wi-Fi,Bluetooth, and/or airplane mode). If an input is received to toggleairplane mode on (e.g., to restrict the electronic device from receivingor transmitting wireless signals), the electronic device optionallytoggles the electronic device to a state which does not affectfunctionality associated with the respective user account if theelectronic device is in a locked state (e.g., restricting user access tothe electronic device). For example, if the electronic device togglesthe airplane mode on (e.g., to restrict the electronic device fromreceiving or transmitting all types of wireless signals), functionalityassociated with the respective user account, such as having access to alocation of the electronic device, would optionally be disabled becausethe electronic is unable to transmit, via wireless signals, a locationof the electronic device. Thus, in some embodiments, in response toreceiving the input to restrict the electronic device from receiving ortransmitting wireless signals, the electronic device does not restrictparticular signals (e.g., Bluetooth signals) that would cause therespective user account to be unable to access a location of theelectronic device, but does restrict other signals (e.g., signalsrequired for streaming music, sending/receiving of emails,sending/receives of text messages, browsing internet applications withcellular data, etc.) . For example, in response to receiving an input totoggle an airplane mode of the electronic device on, Bluetooth signalsoptionally remain (e.g., partially) enabled (e.g., to continue to allowa respective user account to view a location of the electronic device)while other wireless signals (e.g., Wi-Fi, cellular, etc.) are disabledin accordance with the input. In some embodiments, the electronic deviceprovides an indication that Bluetooth signals remain (e.g., partially)enabled on the electronic device by displaying the selectable optioncorresponding to the Bluetooth signal with a visual appearance differentthan the visual appearance corresponding to settings that are on or off.

The above-described manner of continuing to allow a respective useraccount to have access to a location of the electronic when an input isreceived to turn off the transmission or receiving of wireless signalsprovides enhanced security by disabling settings of the electronic thatdo not affect functionality associated with the respective user account,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient, which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the one or more criteria include a criterion thatis satisfied when the electronic device is in a locked state, and is notsatisfied when the electronic device is in an unlocked state (732 a). Insome embodiments, in response to receiving the second input, inaccordance with a determination that the one or more criteria are notsatisfied, the electronic device restricts (732 b) the electronic devicefrom receiving or transmitting wireless signals including preventing theuser account from having access to the location of the electronicdevice, such as in FIG. 6EE touch contact 622 toggling off Bluetooth,and in response, Bluetooth is toggled off in FIG. 6FF. For example, ifthe second input corresponding to the request to enable a mode thatrestricts the electronic device from receiving or transmitting wirelesssignals is receive while the device is unlocked (e.g., user access tothe electronic device is not being restricted), the electronic device isunable to receive or transmit wireless signals including the wirelesssignals that allows a respective user account to have access to thephysical location of the electronic device. In some embodiments, thesecond input is received while the electronic device is displaying auser interface that includes selectable (e.g., toggle-able) options forcontrolling if the electronic device is able to receive particularwireless signals (e.g., Wi-Fi, Bluetooth, cellular) and selectableoption for controlling if the electronic is able to receive/transmit alltypes of wireless signals. In some embodiments, if an input is receivedselecting a selectable option for controlling if the electronic is ableto receive/transmit all types of wireless signals and the selectableoption is toggled on (e.g., the electronic device is currently able totransmit or receive wireless signals), the electronic device switches toa mode that restricts the electronic device from receiving/transmittingall (or at least the signals that were disabled when the device waslocked, and additional signals or functionalities that were not disabledwhen the device was locked) types of wireless signals, which in turnrestricts the respective user from accessing the location of theelectronic device. In some embodiments, if an input is receivedselecting the selectable option for controlling if the electronic isable to receive/transmit all (or more) types of wireless signals and theselectable option is toggled off (e.g., the electronic device iscurrently not able to transmit or receive wireless signals), theelectronic device switches to a mode that allows the electronic deviceto receive/transmit all (or the more) types of wireless signals, whichin turn, allows the respective user account access to the location ofthe electronic device.

The above-described manner of preventing the respective user accountfrom having access to a location of the electronic device when input isreceived to restrict the electronic from receiving and/or transmittingwireless signal while the electronic device is unlocked providesenhanced security by only allowing authorized users of the electronicdevice to prevent a respective user account from having access to thelocation of the electronic device, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 7A-7H have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 900, 1100, 1300 and 1500) are also applicable in an analogousmanner to method 700 described above with respect to FIGS. 7A-7H. Forexample, the association of the electronic device with a user accountand/or its ability to be tracked by the user account described abovewith reference to method 700 optionally have one or more of thecharacteristics of tracking objects or devices, etc., described hereinwith reference to other methods described herein (e.g., methods 900,1100, 1300 and 1500). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., a as described with respect to FIGS. 1A-1B, 3, 5A-5H)or application specific chips. Further, the operations described abovewith reference to FIGS. 7A-7H are, optionally, implemented by componentsdepicted in FIGS. 1A-1B. For example, detecting operation 702 a anddisplaying operation 702 b are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch screen 504, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on the touchscreen corresponds to a predefined event or sub-event, such as selectionof an object on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

Notification of Separation From a Remote Locator Object or Device

Users interact with electronic devices in many different manners. Insome embodiments, an electronic device is able to track the location ofan object such as a remote locator object and/or another electronicdevice configured to be tracked by the electronic device. In someembodiments, the remote locator object (and/or device), which supportslocation tracking functions, can be attached to items that do notsupport location tracking functions. The embodiments described belowprovide ways in which an electronic device provides an alert that aremote locator object that is associated with the user has becomeseparated from the user, thus enhancing the user's interactions with theelectronic device. Enhancing interactions with a device reduces theamount of time needed by a user to perform operations, and thus reducesthe power usage of the device and increases battery life forbattery-powered devices. It is understood that people use devices. Whena person uses a device, that person is optionally referred to as a userof the device.

FIGS. 8A-8T illustrate exemplary ways in which an electronic devicedisplays notifications of a separation with a remote locator object(and/or device) in accordance with some embodiments of the disclosure.The embodiments in these figures are used to illustrate the processesdescribed below, including the processes described with reference toFIGS. 9A-9J.

FIGS. 8A-8T illustrate an electronic device 500 displaying notificationsof separation from one or more remote locator objects. The figuresillustrate separation from remote locator object(s), but it isunderstood that the electronic device is optionally similarlyconfigurable to generate notifications of separation from one or moreelectronic device devices (e.g., left and/or right earbuds, smart watch,laptop, tablet computer, etc.), and optionally responds in the samemanner as illustrated in FIGS. 8A-8T to such separations.

FIG. 8A illustrates an exemplary device 500 that includes touch screen504. As shown in FIG. 8A, the electronic device 500 presents a lockscreen user interface 800 (e.g., a wake screen user interface). In someembodiments, lock screen user interface 800 is the user interface thatis displayed when electronic device 500 is awoken (e.g., from a sleep(low power) or locked state). One or more of the examples described withreference to FIGS. 8A-8T describe notifications displayed by device 500while device 500 is displaying the lock screen user interface 800, butit is understood that in some embodiments, device 500 similarly displaysthe illustrated notifications while device 500 is displaying other userinterfaces (e.g., a home screen user interface, such as described withreference to FIG. 4A, a user interface of an application installed ondevice 500, etc.).

As mentioned previously, device 500 is optionally able to displaynotifications when an object or a device is separated from the device500 (e.g., separated from a location corresponding to the user of device500). In some embodiments, the object is referred to as a remote locatorobject. A remote locator object is optionally a device with a battery,one or more wireless antenna and a processor (e.g., a low powerprocessor) that enable the device to function as a special-purposeremote locator object when associated with or attached to anotherphysical object (e.g., wallet, purse, backpack, suitcase, car, set ofkeys, or the like). In some embodiments, the remote locator object is amulti-purpose device with location tracking capabilities such as asmartphone, tablet, computer, or watch. In some embodiments, a remotelocator object is capable of transmitting location data to theelectronic device. For example, a remote locator object optionallyincludes a GPS locator. In some embodiments, a remote locator objectdoes not include location tracking capability and relies on otherelectronic devices to receive location data. In some embodiments, aremote locator object is able to wirelessly communicate with otherelectronic devices, such as the electronic device 500 (e.g., overBluetooth, RF, IR, NFC, Wi-Fi, etc.).

In some embodiments, the trigger that causes device 500 to generate aseparation alert that indicates that a given object has been separatedfrom device 500 is different depending on one or more movementcharacteristics of device 500 and/or the object when (or before) theseparation occurs. For example, in some embodiments, when device 500and/or the object have settled down at a location (e.g., moved less thana threshold distance (e.g., 3, 5, 10, 30 feet) during a threshold amountof time (e.g., 1, 5, 10, 20, 30 minutes) after arriving at thatlocation), the trigger used by device 500 to generate a separation alertis optionally based on a geofence that is established (e.g., by device500) at that location once device 500 and the object have settled downat that location.

In particular, with reference to FIG. 8A, as shown in map 811 a, device500 (represented by “Phone” in maps 811) and the object have arrived atlocation 804. In some embodiments, a Bluetooth connection (or otherwired or wireless connection) is active between device 500 and theobject, as indicated by the unbroken line between device 500 and theobject in schematic 802 a. The schematics 802 in the figures optionallycorrespond to any one of a number of signals that can be used asindicative of separation between device 500 and the object. For example,in some embodiments, a loss or reduction below a threshold strength(e.g., 1%, 5%, 10%, 30%, 50%) of the Bluetooth (or other) connectionbetween device 500 and the object is a signal that is indicative ofseparation between device 500 and the object. In some embodiments,additionally or alternatively, if the object is a magnetic accessorythat attached to device 500 magnetically, the determination by device500 that the accessory is not (or no longer) attached to device 500 is asignal that is indicative of separation between device 500 and theobject. Device 500 responds in various ways to such signals, as isdescribed herein.

In FIG. 8A, after having settled at location 804 as previouslydescribed, device 500 and/or the object define geofence 806 aroundlocation 804, as shown in map 811 b. In some embodiments, location 804is at the center of the geofenced area 806. In some embodiments, theradius of the geofenced area is 3, 5, 10, 20, 40, 50, or 100 feet. Inmap 811 c, device 500 has moved away from the object to a distancesufficient to break the Bluetooth connection between device 500 and theobject, as shown in schematic 802 c with the broken line between device500 and the object. However, device 500 remains within geofence 806.Therefore, device 500 does not generate a separation alert, as shown inFIG. 8A.

In FIG. 8B, similar to FIG. 8A, device 500 and the object have settledat location 804, and a geofence 806 has been established around thatlocation, as shown in maps 813 a and 813 b. In map 813 c, device 500 hasmoved away from the object to a distance sufficient to break theBluetooth connection between device 500 and the object, as shown inschematic 802 c, and in contrast to FIG. 8A, device 500 has just exitedgeofence 806 (e.g., determined based on a GPS and/or location sensor ondevice 500). In response to device 500 exiting geofence 806, device 500generates (e.g., displays on touch screen 504) separation alert 808. Insome embodiments, device 500 generates separation alert 808 in thescenario of FIG. 8B regardless of whether the Bluetooth (or other)connection between device 500 and the object is broken. In someembodiments, device 500 only generates separation alert 808 in thescenario of FIG. 8B if the Bluetooth (or other) connection betweendevice 500 and the object is broken. For example, if the object is anaccessory (e.g., magnetic or otherwise) of device 500 that attaches(e.g., magnetically or otherwise) to device 500, in the scenario of FIG.8B, device 500 optionally generates a separation alert for the objectif, upon exiting the geofence 806, the object is detached from device500.

Separation alert 808 in FIG. 8B indicates that the object has been leftbehind, and includes a map 810 of the last known location of the object(e.g., indicated by an icon associated with the object being displayedat a location on the map 810 that corresponds to the last known locationof the object). In some embodiments, the last known location of theobject is the location at which device 500 last detected the objectprior to exiting geofence 806, or is the location at which device 500last detected object even after exiting geofence 806.

Separation alert 808 also includes selectable option 812 a that isselectable to display additional information about the object (as willbe described in more detail later), selectable option 812 b that isselectable to configure device 500 to no longer generate separationalerts for the object if it is left behind at the last known location ofthe object (e.g., to designate the last known location of the object asa trusted location for that object, as will be described in more detaillater), and selectable option 812 c that is selectable to configuredevice 500 to no longer generate separation alerts for the object, evenif the various criteria for generating a separation alert for the objectwould have otherwise been met (as will be described in more detaillater).

In some embodiments, if device 500 and/or the object are moving or haverecently been moving at the time of separation from each other, ratherthan utilizing a geofence to trigger the generation of separationalerts, device 500 utilizes the Bluetooth (or other) connection statusbetween device 500 and the object to generate the separation alert. Forexample, in FIG. 8C, device 500 and the object are moving from location804 a shown in map 815 a to location 804 b shown in map 815 b. In map815 c, device 500 has continued moving while the object remains atlocation 804 b; and, due to the continued movement of device 500, theBluetooth (or other) connection between device 500 and the object hasbeen lost, as indicated in schematic 802 c. In some embodiments, becausedevice 500 and the object were recently (e.g., within the past 5, 10,15, 20, 30 minutes) moving together (e.g., while remaining within 0.5,1, 2, 3, 5, 10 feet of one another) at the time of the loss of theconnection between device 500 and the object, in response to detectingthe loss of the connection between device 500 and the object, device 500generates separation alert 808 for the object, as shown in FIG. 8C. Aspreviously mentioned, it is understood that the status of the connectionbetween device 500 and the object could correspond to an attachmentstatus between device 500 and the object (e.g., if the object is anaccessory that attaches to device 500, magnetically or otherwise), andthat a lost connection between the two items as described herein couldcorrespond to detection by device 500 that the object has been detachedfrom device 500—in such embodiments, device 500 would optionally respondin the same manner as described herein with respect to the loss of aBluetooth connection between device 500 and the object.

In FIG. 8C, as previously described, separation alert 808 includes a map810 of the last known location of the object, selectable option 812 athat is selectable to display additional information about the object,and selectable option 812 c that is selectable to configure device 500to no longer generate separation alerts for the object. In someembodiments, if device 500 generates the separation alert 808 whiledevice 500 and/or the object are moving or have recently moved (e.g., ifdevice 500 generates the separation alert 808 based on the Bluetooth (orother) connection status between device 500 and the object, rather thanbased on a geofence as described with reference to FIGS. 8A-8B), theseparation alert 808 does not include a selectable option to designatethe last-known location of the object as a trusted location for thatobject. The separation alert 808 optionally does not include such anoption, because if device 500 and/or the object were moving or recentlymoving when the separation between the two items occurred, thelast-known location for the object is likely different from the actualcurrent location of the object and/or the last-known location for theobject is likely not a location that would be likely to be designated asa trusted location for the object.

In some embodiments, the separation alert 808 generated by device 500for a given object only includes options 812 b and/or 812 c the first N(e.g., 1, 2, 3, 5, 10) times a separation alert is generated for thatobject (e.g., whether based on Bluetooth (or other) connection status,or based on a geofence). In subsequent separation alerts for thatobject, device 500 optionally does not include options 812 b and/or 812c in the separation alert. For example, in FIG. 8D, device 500 and theobject have been separated in the same manner as in FIG. 8C, subsequentto the separation illustrated in FIG. 8C. Because the separation alert808 in FIG. 8D is the second (or Nth) separation alert generated for theobject by device 500, the separation alert 808 does not include options812 b and/or 812 c, as shown in FIG. 8D.

In some embodiments, in order for device 500 to generate a separationalert for a given object, device 500 and the object must have left atrusted location (e.g., previously designated for that object by theuser) together prior to the separation of device 500 and the object(e.g., before the separation, but on the same day as the separation;before the separation, but in the same hour as the separation; beforethe separation, but in the same week as the separation; etc.). Forexample, in FIG. 8E, as shown in map 819 a, a trusted location 814 hasbeen designated (e.g., for the object). Trusted location 814 optionallycorresponds to the location of the user's home, the location of theuser's work, the location of the user's gym, etc. As shown in map 819 a,device 500 and the object are both within trusted location 814 atlocation 804 a within trusted location 814. As shown in map 819 b,device 500 and the object both move and leave trusted location 814together to location 804 b. While moving (or after having recentlymoved), the Bluetooth (or other) connection between device 500 and theobject has been lost, as shown in map 819 c and schematic 802 c. Inresponse, because device 500 and the object both left trusted location814 together prior to (e.g., earlier in the day of) the separation ofthe object from device 500 shown in map 819 c, device 500 generatesseparation alert 808, as shown in FIG. 8E.

In contrast, in FIG. 8F, device 500 and the object did not leave atrusted location together; therefore, device 500 does not generate aseparation alert when the Bluetooth (or other) connection between device500 and the object is lost. In particular, as shown in map 821 a, device500 is at location 816 within trusted location 814, while the object isat location 804 outside of the trusted location 814. In map 821 a, theBluetooth (or other) connection between device 500 and the object is notestablished, as indicated in schematic 802 a. As shown in map 821 b,device 500 exits trusted location 814 without the object, and joins theobject at location 804. In map 821 b, the Bluetooth (or other)connection between device 500 and the object is active or established,as indicated in schematic 802 b. In map 821 c, device 500 separates fromthe object (similar to map 819 c in FIG. 8E), which causes the Bluetooth(or other) connection between device 500 and the object to be lost, asindicated in schematic 802 c. In response to the loss of the connectionbetween device 500 and the object, device 500 does not generate aseparation alert in FIG. 8F (as it did in FIG. 8E), because device 500and the object did not leave a trusted location together prior to theseparation of device 500 and the object. In some embodiments, therequirement that device 500 and the object of interest leave a trustedlocation together helps to reduce the number of unnecessary separationalerts that might be generated for objects that separate from device 500in a given period of time (e.g., a day) by restricting those separationsthat trigger the generation of separation alerts to be with respect toobjects that, for example, started the day at a trusted location withdevice 500.

Device 500 is optionally able to generate separation alerts in thecontext of multiple objects, as will be described with reference toFIGS. 8G through 8J-2. For example, in FIG. 8G, as shown in map 823a,device 500 and Object 1 are at location 816 within trusted location 814.Object 2 is at location 804 outside of trusted location 814. TheBluetooth (or other) connection between device 500 and Object 1 isactive, and the Bluetooth (or other) connection between device 500 andObject 2 is not active, as indicated in schematic 802 a. In map 823 b,device 500 and Object 1 leave trusted location 814 together, move tolocation 804 together, which is where Object 2 is located. In map 823 b,the Bluetooth (or other) connections between device 500 and Objects 1and 2 are active, an indicative in schematic 802 b. While moving (orafter having recently moved), device 500 moves away from Objects 1 and2, which both remain at location 804, as shown in map 823 c, and theBluetooth (or other) connections between device 500 and Objects 1 and 2are lost, as indicated in schematic 802 c. In response to the loss ofthe Bluetooth (or other) connections between device 500 and Objects 1and 2, device 500 generates separation alert 808, as shown in FIG. 8G.Separation alert 808 is only for Object 1 and not for Object 2, becauseonly Object 1 left a trusted location 814 together with device 500(e.g., earlier that day) prior to the separation of device 500 fromObjects 1 and 2.

In contrast, in FIG. 8H, device 500, Object 1 and Object 2 all leavetrusted location 814 together, as shown in map 825 a. Device 500 is,similar to FIG. 8G, separated from both Objects 1 and 2, which remain atlocation 804, in map 825 c while device 500 was moving (or was recentlymoving). In response to the loss of the Bluetooth (or other) connectionsbetween device 500 and Objects 1 and 2 (as indicated in schematic 802c), device 500 generates separation alert 808, as shown in FIG. 8H.Separation alert 808 in FIG. 8H is for both Objects 1 and 2 (e.g., acombined separation alert), because the criteria for generating aseparation alert was satisfied for both Objects 1 and 2, including therequirement that the objects leave a trusted location together withdevice 500 prior to the separation. The combined separation alert 808 inFIG. 8H includes an indication that both Objects 1 and 2 have been leftbehind, a map that indicates the location(s) of Objects 1 and 2, andselectable option 812 a that is selectable to display more informationabout Objects 1 and 2. It is understood that while the requirement forleaving a trusted location has been illustrated in the context ofseparation alerts triggered by the Bluetooth (or other) connectionstatus between device 500 and object(s), the requirement is optionallysimilarly applicable to separation alerts triggered based ongeofence(s).

FIG. 81 illustrates another scenario involving multiple objects. In FIG.81, device 500 and Objects 1 and 2 have settled down at location 804, asshown in map 827 a. The Bluetooth (or other) connections between device500 and Objects 1 and 2 are active, as indicated in schematic 802 a. Inresponse to having settled down, geofence 806 is established as shown inmap 827 b, as previously described. While geofence 806 is established,device 500 moves and exits geofence 806 while Objects 1 and 2 remain atlocation 804, as shown in map 827 c. At the time device 500 exitsgeofence 806, the Bluetooth (or other) connections between device 500and Objects 1 and 2 have already been lost, as indicated by schematic802 c.

In response to exiting geofence 806, device 500 generates separationalert 808, as shown in FIG. 81. Separation alert 808 in FIG. 81 is acombined separation alert for Objects 1 and 2 that indicates that bothobjects have been left behind, and that includes a map 810 of thelocations of Objects 1 and 2 and selectable option 812 a that isselectable to display additional information about Objects 1 and 2, aspreviously described. The separation alert 808 of FIG. 81 also includesselectable options 812 b and 812 c (e.g., because the separation alertis the Nth or less separation alert for one or more of Objects 1 and 2).While the inclusion of selectable options 812 b and 812 c are shown inthe context of a geofenced-based combined separation alert, it isunderstood that Bluetooth (or other) connection status-based combinedseparation alerts optionally also include selectable option 812 c (e.g.,if the separation alert is the Nth or less separation alert for one ormore of Objects 1 and 2). Selectable option 812 b is optionallyselectable to designate the current location 804 of Objects 1 and 2 as atrusted location for both Objects 1 and 2. Selectable option 812 c isoptionally selectable to configure device 500 to not generate separationalerts for either of Objects 1 and 2.

In FIG. 8J-1, device 500, Object 1 and Object 2 have all settled down atlocation 804, as indicated in map 829a and as in FIG. 81. The Bluetooth(or other) connections between device 500 and Objects 1 and 2 areactive, and indicated by schematic 802 a. In map 829 b, as in FIG. 81,geofence 806 is established. In map 829 c, device 500 and Object 2 exitgeofence 806 together, while Object 1 remains at location 804 withingeofence 806. Further, as indicated by schematic 802 c, the Bluetooth(or other) connection between device 500 and Object 2 is active at thetime device 500 and Object 2 exit geofence 806, and the Bluetooth (orother) connection between device 500 and Object 1 is lost (or hasalready been lost) at the time device 500 and Object 2 exit geofence806.

In response to exiting geofence 806, device 500 generates separationalert 808 as shown in FIG. 8J-1. Separation alert 808 is only for Object1, and not for Object 2, because Object 2 remains with device 500 whendevice 500 exits geofence 806. Further, in addition to indicating thatObject 1 has been left behind, and indicating the last known locationfor Object 1, the separation alert includes selectable option 812 a thatis selectable to display additional information about Object 1 (but notObject 2), selectable option 812 b that is selectable to designatelocation 804 as a trusted location for Object 1 (but not Object 2), andselectable option 812 c that is selectable to configure device 500 tonot generate separation alerts for Object 1 (e.g., while continuing togenerate separation alerts for Object 2).

In some embodiments, device 500 and/or object(s) continue to establishnew geofences as they settle down at new locations, whether or not priorgeofences triggered the generation of separation alerts (e.g., whetheror not objects have been left behind at prior geofence locations). Forexample, in FIG. 8J-2, after geofence 806 has been established andObject 1 has been left behind (e.g., and a separation alert has beengenerated for Object 1), as described with reference to FIG. 8J-1 and asindicated by the shaded geofence 806 in map 831 a, device 500 and Object2 settle down at location 805, and geofence 807 is established aroundlocation 805, as shown in map 831 b. While geofence 807 is established,device 500 moves and exits geofence 807 while Object 2 remains atlocation 805 within geofence 807. In response to exiting geofence 807,device 500 generates separation alert 808, which is a separation alertonly for Object 2 and not for Object 1. The separation alert optionallyincludes one or more of the elements previously described, including amap 810 that indicates the location of Object 2 (and not Object 1), aselectable option 812 a that is selectable to display additionalinformation about Object 2 (and not Object 1), a selectable option 812 bthat is selectable to designate the last known location for Object 2 asa trusted location for Object 2 (but not for Object 1), and selectableoption 812 c that is selectable to configure device 500 to not generateseparation alerts for Object 2 (e.g., while continuing to generateseparation alerts for Object 1).

Various user interfaces that are accessible from the separation alertsdescribed herein (e.g., with reference to FIGS. 8A through 8J-2) willnow be described. For example, in FIG. 8K, device 500 detects selectionof selectable option 812 b (e.g., via a tap of contact 803) inseparation alert 808 for an object. In response, device 500 displaysuser interface 820 for designating the last known location for thatobject as a trusted location for that object, as shown in FIG. 8L. Userinterface 820 includes a map 822 that includes an indication of theproposed trusted location 824 for the object that includes (e.g., iscentered around) the last known location for the object. User interface820 also includes a selectable option 826 a that is selectable todisplay additional information about the object (e.g., the same orsimilar information as would be displayed in response to selection ofselectable option 812 a in FIG. 8K), and a selectable option 826 b thatis selectable to initiate a process for the user of device 500 to editthe proposed trusted location 824 for the object (e.g., editing thesize, location, name, etc. of the proposed trusted location 824). Insome embodiments, in response to detecting selection of “Done” in userinterface 820, device 500 designates the proposed trusted location 824as a trusted location for the object, and in response to detectingselection of “Cancel” in user interface 820, device 500 does notdesignate the proposed trusted location 824 as a trusted location forthe object.

FIG. 8M illustrates the separation alert 808 of FIG. 8K. In FIG. 8M,device 500 detects selection of selectable option 812 a for displayingadditional information about the object (e.g., via a tap of contact803). In response to the selection of selectable option 812 a, device500 displays user interface 828 (e.g., of an object and/or devicelocation tracking application installed on device 500, as described inthis disclosure). User interface 828 includes a representation of a mapthat includes the last known location for the object, a representation(e.g., icon) 830 of the object at a location on the map corresponding tothe last known location for the object, and user interface element or“card” 832 for the object. User interface element 832 includesinformation 834 about the object, including one or more of arepresentation (e.g., icon) of the object, an indication of the lastknown location of the object (e.g., “Near Main St.”), or an indicationof a time at which the last known location of the object was lastupdated (e.g., “Last Seen 5m [minutes] ago”).

If the object has been determined by device 500 to have been left behindat a location (e.g., based on a geofence or based on a Bluetooth (orother) connection status between device 500 and the object), userinterface element 832 for the object also includes a selectable option836 that is selectable to designate the last known location of theobject as a trusted location for the object. Selectable option 836optionally also includes an indication of the last known location of theobject, such as an address of the last known location of the object.User interface 832 also includes a selectable option 838 that isselectable to cause the object to emit an audible sound (e.g., to aid auser in locating the object), and a selectable option 840 that isselectable to initiate a process to locate the object, as is describedin more detail with reference to methods 1100 and 1300. Selectableoption 840 optionally includes an indication of a current distancebetween device 500 and the last known location of the object, and anindication of an estimated time for walking/driving/cycling/etc. fromthe current location of device 500 to the last known location of theobject.

In FIG. 8N, device 500 detects selection of selectable option 836 (e.g.,via a tap of contact 803). In response, device 500 displays userinterface 820, as shown in FIG. 80. User interface 820 in FIG. 80optionally has one or more of the characteristics of user interface 820in FIG. 8L.

FIG. 8P illustrates user interface 828, as previously described. In someembodiments, user interface element 832 includes a trusted locationsregion 842, as shown in FIG. 8P, that indicates the trusted locations(if any) that have been designated for the object with which userinterface 832 is associated. In FIG. 8P, device 500 detects touchdown ofcontact 803 in user interface element 832, and movement of contact 803upward on touch screen 504, as shown in FIG. 8Q. In response, device 500displays more of user interface element 832 as it has been draggedupwards in user interface 828, as shown in FIG. 8Q. As shown in FIG. 8Q,the trusted locations region 842 of user interface element 832 includesa listing of trusted locations that have already been designated for theobject (e.g., “Home”, which optionally corresponds to the home addressof the user of device 500), and a selectable option 844 that isselectable to manage the locations that are designated as trustedlocations for the object.

In FIG. 8R, device 500 detects selection of selectable option 844. Inresponse, device 500 displays user interface 846, as shown in FIG. 8S,which is a user interface for managing the trusted locations for theobject. User interface 846 includes a first region that includesrepresentations of the current trusted locations for the object (e.g.,representation 848 corresponding to “Home”), and a second region thatincludes representations of trusted locations that are suggested bydevice 500 as potential trusted locations for the object. The firstregion also includes a selectable option 850 that is selectable for theuser to manually designate a trusted location for the object.Representation 848 is optionally selectable to display additionalinformation about the “Home” trusted location (e.g., an address for“Home”, a map of the area including “Home”, the object(s) for which“Home” is designated as a trusted location, etc.), and representation(s)of suggested trusted locations in the second region are optionallysimilarly selectable to display additional information about thoserespective suggested trusted locations.

As mentioned above, the second region of user interface 846 includesrepresentations of one or more suggested locations as potential trustedlocations for the object. The locations included in the second regionare optionally locations that are already designated as trustedlocations for other objects or devices associated with the user ofdevice 500 and/or for which device 500 is configured to track locationsand/or generate separation alerts. For example, in FIG. 8S, userinterface 846 includes representation 852 corresponding to the “Gym”trusted location, representation 854 corresponding to the “Office”trusted location, and representation 856 corresponding to the “CoffeeShop” trusted location. Representations 852, 854 and 856 optionallyinclude information about which objects and/or how many objects usetheir respective locations as trusted locations. For example,representation 852 includes an indication of how many other objects(other than the object with which user interface 846 is associated) usethe “Gym” as a trusted location. Additionally or alternatively,representation 854 includes an indication that the “Office” is used byObject 2 and Device 3 as a trusted location, and representation 856includes an indication that the “Coffee Shop” is used by Object 2 as atrusted location. In some embodiments, if none of the other objects ordevices associated with the user of device 500 and/or for which device500 is configured to track locations and/or generate separation alertshas a trusted location designated, user interface 846 does not includesuggested trusted locations for the object.

In some embodiments, representations 852, 854 and 856 (or the (+)indications in representations 852, 854 and 856) are selectable todesignate their corresponding locations as a trusted location for theobject. For example, in FIG. 8S, device 500 detects selection ofrepresentation 856 (e.g., via a tap of contact 803). In response, device500 designates the “Coffee Shop” as a trusted location for the object,as shown in FIG. 8T. Representation 856 of the “Coffee Shop” is removedfrom the second region of user interface 846, and is now displayed inthe first region of user interface 846. Further, representations oftrusted locations in the first region (or the (−) indications in therepresentations of trusted locations) are optionally selectable toremove those locations as trusted locations for the object. For example,in FIG. 8T, if device 500 were to detect selection of representation856, device 500 would optionally remove the “Coffee Shop” as a trustedlocation for the object, would remove representation 856 from the firstregion of user interface 846, and would optionally displayrepresentation 856 in the second region of user interface 846. In someembodiments, because at least one trusted location is required for anobject for device 500 to generate separation alerts for that object (aspreviously described), device 500 does now allow all trusted locationsto be removed for the object in user interface 846. In some embodiments,device 500 does not allow removal of the “Home” trusted location (asshown in FIG. 8T by the lack of a (-) indication in representation 848).In some embodiments, device 500 instead prevents the removal of thelast-remaining trusted location for the object.

FIGS. 9A-9J are flow diagrams illustrating a method 900 of displayingnotifications of a separation with a remote locator object (and/ordevice) in accordance with some embodiments, such as in FIGS. 8A-8T. Themethod 900 is optionally performed at an electronic device such asdevice 100, device 300, or device 500 as described above with referenceto FIGS. 1A-1B, 2-3, 4A-4B and 5A-5H. Some operations in method 900 are,optionally combined and/or order of some operations is, optionally,changed.

As described below, the method 900 provides ways to displaynotifications of a separation with a remote locator object (and/ordevice). The method reduces the cognitive burden on a user wheninteracting with a user interface of the device of the disclosure,thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, increasing the efficiency of theuser's interaction with the user interface conserves power and increasesthe time between battery charges.

In some embodiments, method 900 is performed at an electronic device(e.g., device 500) in communication with one or more wireless antenna,an output component, and one or more input devices (e.g., a mobiledevice (e.g., a tablet, a smartphone, a media player, or a wearabledevice) including wireless communication circuitry, optionally incommunication with one or more of a mouse (e.g., external), trackpad(optionally integrated or external), touchpad (optionally integrated orexternal), remote control device (e.g., external), another mobile device(e.g., separate from the electronic device), a handheld device (e.g.,external), and/or a controller (e.g., external), etc. In someembodiments, the display generation component is a display integratedwith the electronic device (optionally a touch screen display), externaldisplay such as a monitor, projector, television, or a hardwarecomponent (optionally integrated or external) for projecting a userinterface or causing a user interface to be visible to one or moreusers, etc.).

In some embodiments, the electronic device detects (902 a) a change in alocation of a remote locator object relative to a location associatedwith the user, such as “Phone” and “Object 1” and/or “Object 2” changinglocations relative to one another in FIGS. 8A through 8J-2 (e.g.,detecting a change in the location of the electronic device while theremote locator object remains stationary, detecting a change in thelocation of the remote locator object while the electronic deviceremains stationary, or detecting that the remote locator object and theelectronic device moved in different directions or by differentamounts). In some embodiments, detecting the change includes monitoring(e.g., continuously or periodically) the position of the remote locatorobject (e.g., absolute position or position relative to the electronicdevice) and/or the position of the device (e.g., absolute position orposition relative to the remote locator object). In some embodiments,the location information is obtained via one or more sensors such as aGPS locator, a compass, etc. In some embodiments, a remote locatorobject is capable of transmitting location data to the electronicdevice. For example, a remote locator object optionally includes a GPSlocator. In some embodiments, a remote locator object does not includelocation tracking capability and relies on other electronic devices toreceive location data. In some embodiments, the indication of the changein location of the remote locator object is received from a server oranother electronic device. In some embodiments, the detecting of thechange in the location of the remote locator object occurs while theremote locator object is associated with a user. In some embodiments,the remote locator object is setup to be associated with the user of theelectronic device. In some embodiments, a remote locator object is adevice with a battery, one or more wireless antenna and a processor(e.g., a low power processor) that enables the device to function as aspecial-purpose remote locator object when associated with anotherphysical object (e.g., wallet, purse, backpack, suitcase, car, set ofkeys, or the like). In some embodiments, the remote locator object is amulti-purpose device with location tracking capabilities such as asmartphone, tablet, computer, or watch. In some embodiments, a remotelocator object is capable of transmitting location data to theelectronic device. For example, a remote locator object optionallyincludes a GPS locator. In some embodiments, a remote locator objectdoes not include location tracking capability and relies on otherelectronic devices to receive location data. In some embodiments, aremote locator object is able to wirelessly communicate with otherelectronic devices, such as the electronic device (e.g., over Bluetooth,RF, IR, NFC, Wi-Fi, etc.). In some embodiments, the remote locatorobject has an uninitialized state and an initialized state. For example,when the remote locator object is first manufactured, the remote locatorobject is in an uninitialized state. In the uninitialized state, theremote locator object is optionally not assigned a label and/orassociated with any particular user, user account or electronic device.In the initialized state, the remote locator object is optionallyassigned a label and/or associated with a respective user, user accountand/or electronic device (e.g., the electronic device).

In some embodiments, in response to detecting the change in location ofthe remote locator object relative to the location associated with theuser (902 c), in accordance with a determination that the locationassociated with the user and the location of the remote locator objecthave been moving together recently (e.g., such as Phone and Objectmoving together recently in FIG. 8C), and that first separation criteriaare met, such as the connection between Phone and Object being broken asindicated in schematic 802 c in FIG. 8C (e.g., if the user and theremote locator object have recently (e.g., within the past 5 minutes, 30minutes, 1 hour, 3 hours, 8 hours, 12 hours, etc.) been within athreshold distance of each other (e.g., 6 inches, 1 foot, 3 feet, 10feet, etc.) and have moved (e.g., more than a threshold amount) together(e.g., moved while not becoming further than the threshold distanceapart). In some embodiments, the first separation criteria includes arequirement that the electronic device, the user of the electronicdevice, and/or the remote locator object are currently moving (e.g.,changing locations, optionally moving by at least a threshold amountsuch as more than 3 feet, 10 feet, 30 feet, 200 feet, etc., and/ormoving at a velocity greater than a threshold velocity such as 1, 2, 5,10, 20 feet/second and/or has been moving for a threshold amount of timesuch as 1 minute, 5 minutes, 30 minutes, 1 hour, 2 hours, etc.) and/orhas not been stationary (e.g., has not moved by more than the thresholdamount) for at least a threshold amount of time (e.g., 1 minute, 5minutes, 30 minutes, 1 hour, 2 hours, etc.). In some embodiments, thecriterion is satisfied if either the electronic device or the remotelocator object (or both) are moving (e.g., optionally moving together,within a threshold distance from each other, such as 1 foot, 3 feet, 10feet, 50 feet, etc.) optionally until, for example, the first separationcriteria is satisfied (e.g., until the remote locator object becomesseparated from the electronic device). In some embodiments, the firstseparation criteria are satisfied if the remote locator object and theelectronic device lose wireless connectivity (e.g., Bluetoothconnectivity, NFC connectivity, etc.). For example, the remote locatorobject is paired with the electronic device via a Bluetooth connectionand while the device is in motion, the Bluetooth connection between theremote locator object and the electronic device is lost (e.g., theremote locator object moves out of the effective range of Bluetoothconnectivity such that the Bluetooth connection is broken). In such ascenario, the device optionally determines (e.g., optionally after theconnection has been lost for a threshold amount of time withoutreconnecting, such as 5 seconds, 30 seconds, 1 minute, 5 minutes, etc.),that the remote locator object has been separated from the electronicdevice and thus the first separation criteria are satisfied. Thus, insome embodiments, if the electronic device and the remote locator objectare not stationary for a threshold amount of time, the wirelessconnectivity between the remote locator object and the electronic deviceis used to determine whether the remote locator object is still with theelectronic device or has been separated from the electronic device.),the electronic device generates (902 c), via the output component, aseparation alert at the electronic device without regard to whethersecond separation criteria have been met, wherein the second separationcriteria are different from the first separation criteria, such asseparation alert 808 in FIG. 8C (e.g., displaying a notification orother alert at the electronic device indicating that the remote locatorobject is no longer with the user and/or electronic device and/or thatthe remote locator object has been separated from the user and/orelectronic device). In some embodiments, the notification is selectableto display information associated with the remote locator object, suchas to display the current location or the most recent known location ofthe remote locator object.

In some embodiments, in accordance with a determination that thelocation associated with the user and the location of the remote locatorobject have moved less than a threshold amount for at least a thresholdamount of time (e.g., such as Phone and Object being relativelystationary in FIG. 8B), and that the second separation criteria are met,such as Phone leaving geofence 806 in FIG. 8B (e.g., if the electronicdevice, the user of the electronic device, and/or the remote locatorobject are determined to not be moving and/or are stationary (e.g., notchanging locations, or optionally not moving by at least a thresholdamount such as more than 3 feet, 10 feet, 30 feet, 200 feet, etc.) forat least a threshold amount of time (e.g., 1 minute, 5 minutes, 30minutes, 1 hour, 2 hours, etc.). In some embodiments, the secondseparation criteria are based on the geographical location of the remotelocator object and/or the electronic device. In some embodiments, inresponse to determining that the electronic device and/or the remotelocator object has remained at a respective location (e.g., at aparticular geographic location, at a particular GPS location, at aparticular place of business, at a particular defined location, such ashome or work, etc.) for the threshold amount of time, the location ofthe remote locator object and/or the electronic device is identified asthe settled location of the remote locator object and/or electronicdevice such that if the remote locator object and/or the electronicdevice leave the settled location without the other (e.g., theelectronic device leaves without the remote locator object or the remotelocator object leaves without the electronic device), then it isdetermined that the remote locator object has been separated from theelectronic device and the second separation criteria are met. Forexample, a geographical “fence” (e.g., a geofence with a predeterminedsize, such as 3 feet, 10 feet, 50 feet, 150 feet, 1/4 mile, or a dynamicsize based on the size of the location where the remote locator objectis determined to be, such as the size of the building, size of thelandmark, etc.) is created around the settled location of the remotelocator object such that if the remote locator object and/or electronicdevice exits the geofence without the other device, an alert istriggered. In some embodiments, if the electronic device and/or remotelocator object move within the area of the settled location (e.g.,within the place of business, within the building, within a thresholddistance such as 3 feet, 10 feet, 50 feet, 150 feet, 1/4 mile, etc.),but do not leave the settled location, then the remote locator object isnot determined to be separated from the electronic device and the secondseparation criteria are not met, optionally even if the remote locatorobject is not near the electronic device (e.g., not within 1 foot, 3feet, 10 feet, 30 feet, etc.) and/or optionally even if the remotelocator object no longer has wireless connectivity with the electronicdevice (e.g., even if the first separation criteria are met).), theelectronic device generates (902 d), via the output component, aseparation alert at the electronic device without regard to whether thefirst separation criteria have been met, such as the separation alert808 in FIG. 8B (e.g., displaying a notification or other alert at theelectronic device indicating that the remote locator object is no longerwith the user and/or electronic device and/or that the remote locatorobject has been separated from the user and/or electronic device). Insome embodiments, the notification is selectable to display informationassociated with the remote locator object, such as to display thecurrent location or the most recent known location of the remote locatorobject. The above-described manner of determining whether a remotelocator object is separated from the user based on either a firstprocess or a second process (e.g., by using the first process if thefirst criteria are satisfied or using the second process if the secondcriteria are satisfied) provides a context-specific method ofdetermining whether the remote locator object has been separated fromthe user, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by using theprocess for determining whether the remote locator object has beenseparated from the electronic device that is suited to the situation,which provides a more accurate and/or a faster method of determiningthat the remote locator object has been separated from the electronicdevice), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, whether the first separation criteria have been metis based at least in part on a signal strength of the remote locatorobject as detected by the electronic device, such as the connectionbetween Phone and Object as indicated by schematic 802 c in FIG. 8C(e.g., if the wireless signal that establishes the wireless connectivitybetween the remote locator object and the electronic device (e.g.,Bluetooth, NFC, Wi-Fi Direct, etc.), falls below a threshold level(e.g., below 50% signal strength, 30% signal strength, 10% signalstrength, no signal, etc.), then the first separation criteria aresatisfied), and whether the second separation criteria have been met isindependent of the signal strength of the remote locator object asdetected by the electronic device (904 a), such as described withreference to FIG. 8B and schematic 802 c in FIG. 8B (e.g., the secondseparation criteria is based on the geographic location of the remotelocator object and/or the electronic device such that if the remotelocator object and/or electronic device leave the geographic locationwithout the other, then the second separation criteria are satisfied,without regard to the signal strength between the remote locator objectand the electronic device). The above-described manner of determiningwhether a remote locator object is separated from the user provides acontext-specific method of determining whether the remote locator objecthas been separated from the user, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by using criteria for determining whether the remotelocator object has been separated from the electronic device that aresuited to the situation, which provides a more accurate and/or a fastermethod of determining that the remote locator object has been separatedfrom the electronic device), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, whether the second separation criteria have beenmet is based at least in part on whether the remote locator object orthe electronic device have exited a geofenced region, such as Phoneleaving geofence 806 in FIG. 8B, and whether the first separationcriteria have been met is independent of the geofenced region (906 a),such as described with reference to FIG. 8C (e.g., the second separationcriteria is based on the geographic location of the remote locatorobject and/or the electronic device such that if the remote locatorobject and/or electronic device leave the geographic location withoutthe other, then the second separation criteria are satisfied, withoutregard to whether the first separation criteria are met. Similarly, thefirst separation criteria are satisfied optionally without regard towhether the remote locator object and/or the electronic device have lefta given geographic area without the other.). The above-described mannerof determining whether a remote locator object is separated from theuser provides a context-specific method of determining whether theremote locator object has been separated from the user, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by using criteria for determiningwhether the remote locator object has been separated from the electronicdevice that are suited to the situation, which provides a more accurateand/or a faster method of determining that the remote locator object hasbeen separated from the electronic device), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, after generating the separation alert associatedwith the remote locator object, the electronic device detects (908 a),via the one or more input devices, input directed to the separationalert, such as contact 803 in FIG. 8K (e.g., a selection input, such asa tap input on a location associated with a displayed separation alert).In some embodiments, in response to detecting the input directed to theseparation alert (908 b), in accordance with a determination that theinput corresponds to a request to designate a current location of theremote locator object as a trusted location, the electronic deviceinitiates (908 c) a process to designate the current location of theremote locator object as a trusted location, such as user interface 820in FIG. 8L (e.g., in response to the input directed to the separationalert, display a user interface associated with the separation alert).In some embodiments, the user interface includes information associatedwith the separation alert, such as information about the currentlocation of the remote locator object, the previously known location ofthe remote locator object, the distance of the remote locator objectfrom the user/electronic device, and/or the time at which the remotelocator object was separated from the user. In some embodiments, theuser interface includes one or more affordances to perform one or morefunctions, such as to navigate to the remote locator object, to find theremote locator object, to cause the remote locator object to play asound, and/or to add the current location of the remote locator objectas a trusted location for the remote locator object. In someembodiments, a trusted location is a location at which separation alertsare not triggered if a separation alert would otherwise be generated(e.g., if any of the separation criteria are satisfied), except that theremote locator object is within a threshold radius/distance of thetrusted location (e.g., within 6 inches, 1 foot, 3 feet, 20 feet, 100feet, etc.). In some embodiments, the radius of the trusted location isadjustable by the user and each trusted location has its own set radius.In some embodiments, the radius of the trusted location is automaticallysized based on the location of the trusted location. For example, if thetrusted location is a business's building, the size of the trustedlocation is the area of the business's building and if the trustedlocation is a park, the boundary of the trusted location is the boundaryof the park, etc. In some embodiments, each remote locator object and/ordevice has its own unique set of trusted locations. In some embodiments,a trusted location is a trusted person. For example, when a remotelocator object is determined to be with a trusted person (e.g., isfollowing the trusted person's location or is within a certain thresholddistance, such as 6 inches, 1 foot, 3 feet, 20 feet, 100 feet, etc., ofthe trusted person), then a separation alert is not generated. Theabove-described manner of designating a trusted location provides aquick and efficient way of doing so, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by not requiring input for identifying the location ofthe trusted location, and using the current location of the remotelocator object instead), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, before generating the separation alert and beforethe electronic device is configured to generate separation alerts basedon separation of the remote locator object from the electronic device(910 a) (e.g., the user has not yet enabled the generation of separationalerts based on the location of the remote locator object), theelectronic device detects (910 b) that the first separation criteria orthe second separation criteria have been met (e.g., detecting thateither the first or second separation criteria have been met, or anyother trigger condition has been met, such that a separation alert isbeing generated, will be generated, or otherwise would have beengenerated (e.g., if separation alerts were enabled)). In someembodiments, in response to detecting that the first separation criteriaor the second separation criteria have been met (910 c), in accordancewith a determination that one or more criteria are satisfied, includinga criterion that is satisfied based on a number of times the firstseparation criteria or the second separation criteria have been met(e.g., if the first or second separation criteria have never before beensatisfied based on the location of the remote locator object, if this isthe first time the first or second criteria have been satisfied based onthe location of the remote locator object, or if the number of times thefirst or second separation criteria have been satisfied is within athreshold number of times (e.g., first time, first 5 times, first 10times, etc.), then the one or more criteria are satisfied. In someembodiments, the determination is based on the number of times theseparation criteria have been satisfied on the electronic device (e.g.,regardless of whether separation criteria have been satisfied on otherdevices that are also registered to or otherwise associated with theuser). In some embodiments, the determination is based on the number oftimes the separation criteria have been satisfied for the user of thedevice (e.g., across multiple devices registered to or otherwiseassociated with the user).), the electronic device generates (910 d),via the output component, an indication that the electronic device canbe configured to generate separation alerts based on separation of theremote locator object from the electronic device, such as the separationalerts 808 shown in FIGS. 8B-8C (e.g., generate a pop-up, anotification, an alert, etc., that provides information about separationalerts and/or is selectable to configure the device to generateseparation alerts for the remote locator object). In some embodiments,the indication is selectable or otherwise interactable to display a userinterface that includes information about separation alerts andoptionally includes an affordance that is selectable to initiate aprocess to enable separation alerts to be generated on the electronicdevice (e.g., optionally for multiple electronic devices registered tothe user, optionally for all remote locator objects, optionally for onlythe remote locator object that triggered the indication to begenerated). In some embodiments, if the one or more criteria are notsatisfied, the indication that the electronic device can be configuredto generate separation alerts based on separation of the remote locatorobject from the electronic device is optionally not displayed and/or isdisplayed with fewer options for configuring separation alerts for theremote locator object, as will be described below. The above-describedmanner of facilitating configuration of separation alerts provides aquick and efficient way of configuring the electronic device to generateseparation alerts for a remote locator object, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by not requiring separate, potentially erroneousinput, for configuring the electronic device to generate separationalerts for the remote locator object), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, while displaying, via the output component, a userinterface that includes a representation of a map (912 a), such as userinterface 828 in FIG. 8N that optionally shares one or morecharacteristics of user interface 1202 in FIGS. 12A-12TT that isoptionally reachable by selection of selectable option 812 a (e.g., auser interface that optionally includes information about a currentlocation of one or more tracked objects (e.g., remote locator objects,such as the remote locator object, devices, contacts who have sharedlocation information, etc.). In some embodiments, the user interfaceincludes a representation of a map that includes one or morerepresentations (e.g., icons) of tracked objects at respective locationson the representation of the map corresponding to their current or lastknown physical locations), in accordance with a determination that afirst component and a second component that are associated with eachother are currently connected with each other, such as in FIG. 12A(e.g., the first and second components are components of an electronicdevice that can be physically separated from each other and which can bein wireless (e.g., Bluetooth, NFC, Wi-Fi, etc.) communication with eachother. In some embodiments, the first and second components are left andright wireless earbuds. In some embodiments, the left and right wirelessearbuds are currently connected with each other when they are both in astorage and/or charging case, when they are both in respective ears of auser, and/or when they are within a threshold distance (e.g., 1, 2, 3,5, 10, 20, 30, 50 feet—in some embodiments, based on the wirelessconnectivity range of the wireless connectivity protocol with which theyare connected) of each other.), the electronic device indicates (912 b),in the user interface, the first and second components with a first setof one or more indications having a first visual appearance, such asindicating John's Earbuds on map 1204 with indication 1216 (e.g.,displaying the first and second components in the user interface with afirst visual appearance that indicates that the first and secondcomponents are connected with each other (e.g., physically and/orwirelessly)). In some embodiments, the first and second components aregrouped together and treated as one object (e.g., as opposed to twoseparate components of the same object). In some embodiments, theelectronic device displays a single representation of the set of thefirst and second components on the map in the user interface at thelocation of the set of the first and second components (e.g., as opposedto displaying separate representations of each of the first and secondcomponents on the map).

In some embodiments, in accordance with a determination that the firstcomponent and the second component that are associated with each otherare not currently connected with each other, such as John's Left andRight Earbuds in FIG. 12S, the electronic device indicates (912 c), inthe user interface, the first and second components with a second set ofone or more indications having a second visual appearance, differentfrom the first visual appearance, such as indicating John's Left andRight Earbuds with different indications 1221 and 1223 (e.g., if thefirst component and second component are not physically connected witheach other and/or if the first component and second component are notwireles sly connected with each other (e.g., the first and secondcomponents are out of wireless range from each other), then display thefirst and second components in the user interface with a second visualappearance). In some embodiments, the first and second components aredisplayed as separate objects in the user interface (e.g., therepresentation of the map includes a first indicator for the firstcomponent and a second indicator for the second component, eachdisplayed at their respective locations on the map) such that the useris able to see that the location of the first component is differentfrom the location of the second component. The above-described manner ofdisplaying different indications of the first and/or second componentsprovides a quick and efficient way of indicating appropriate locationinformation for the components based on whether the components areconnected with each other, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by not consuming display or processing resources for two separaterepresentations when the components are connected with each other),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, in accordance with the determination that the firstcomponent and the second component that are associated with each otherare not currently connected with each other (914 a) (e.g., determiningthat the first component and second component are separated by a certainamount of distance such that the first component and second componentare not (e.g., cannot possibly be) connected (e.g., wirelessly) witheach other (e.g., more than 50 feet, more than 500 feet, more than 1mile, etc.), and/or receiving information from one or both componentsthat the first component is not able to communicate with the secondcomponent and/or vice versa), while displaying, via the outputcomponent, a first indication corresponding to the first and secondcomponents (e.g., displaying one entry that corresponds to the set thatincludes the first and second components. For example, displaying, in alisting of tracked objects in the map user interface, an item in thelist (e.g., a row in the list) that corresponds to the collection of thefirst and second components), the electronic device detects (914 b), viathe one or more input devices, an input directed to the first indication(e.g., a tap input on a location associated with the entry), such asselection of indication 1208 in FIG. 12S. In some embodiments, inresponse to detecting the input directed to the first indication, theelectronic device displays (914 c), via the output component, a secondindication corresponding to the first component, and a third indicationcorresponding to the second component, such as indications 1252 and 1254in FIG. 12U (e.g., expanding the first entry (e.g., replacing the firstentry, or displaying, optionally near the first entry) a second entryassociated with the first component and a third entry associated withthe second component). For example, if the first and second componentare not connected with each other, selecting the entry associated withthe set causes display of individual entries for each component (e.g.,to treat them as separate components, as opposed to a single unit). Insome embodiments, if the first component and second component areconnected with each other, then selecting the entry does not causedisplay of individual entries for each component in the list of trackedobjects. In some embodiments, the indication of the first component isselectable to display location information for the first component(e.g., separate from location information for the second component), andthe indication of the second component is selectable to display locationinformation for the second component (e.g., separate from locationinformation for the first component). The above-described manner ofexpanding a given entry into two entries corresponding to the first andsecond components provides an ability for a user to specificallyindicate which of two or more associated components is the component ofinterest when the components are not connected with each other (e.g.,not at the same location), which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by not wasting resources on facilitating locating of componentsthat are not of interest), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, in accordance with the determination that the firstcomponent and the second component that are associated with each otherare not currently connected with each other, the electronic devicedisplays (916 a), on the representation of the map, a first indicationcorresponding to the first component at a location on the representationof the map corresponding to a location of the first component (916 b)(e.g., displaying, on the representation of the map, a representation(e.g., icon, image, etc.) of the first component (e.g., left earbud) ata location on the representation of the map corresponding to thedetermined location of the first component (e.g., the current location,the last known location, etc.)), and a second indication correspondingto the second component at a location on the representation of the mapcorresponding to a location of the second component (916 c), such asindications 1221 and 1223 in FIG. 12U (e.g., displaying, on therepresentation of the map, a second representation (e.g., icon, image,etc.) of the second component (e.g., right earbud), different from thefirst representation of the first component, at a location on therepresentation of the map corresponding to the determined location ofthe second component (e.g., the current location, the last knownlocation, etc.). In some embodiments, each representation is selectableto display information and/or perform one or more functions associatedwith the respective component, such as to display the address at whichthe respective component is located, to cause the respective componentto play a sound, to navigate to the respective component, etc.). Theabove-described manner of separately displaying indications of thecomponents provides a quick and efficient manner of indicatingindividualized location information for the different components, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient, which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, while displaying, via the output component, afinding user interface, providing an option to switch between findingthe first component and finding the second component (918 a), such asfinding interface 1240 in FIG. 12AA including options 1250 and 1252 thatis reachable in response to selection of option 1264 in FIG. 12Z oroption 1230 in FIG. 12TT, which optionally corresponds to option 840 inFIG. 8N (e.g., while performing a process to find the first and/or thesecond component, displaying a finding user interface that includes oneor more options to select which component of the collection of thefirst, second, etc. components to find). For example, the finding userinterface includes a first representation of the first component and asecond representation of the second component, both of which areselectable to cause the process to find the respective component (e.g.,and not the other component). In some embodiments, the finding userinterface includes the option to switch between finding the firstcomponent and second component if the first and second component are notcurrently connected with each other and the finding user interface doesnot include the option to switch between finding the first component andthe second component if the first and second components are currentlyconnected with each other (e.g., the finding user interface displaysinformation for finding the collection of the first, second, third, etc.components, rather than displaying information for finding individualones of the first, second, third, etc. components). In some embodiments,the finding user interface has one or more of the characteristics of thefinding user interface of methods 1100 and/or 1300. The above-describedmanner of providing for options to switch between finding the first orsecond components provides a quick and efficient manner of findingdifferent components of associated components, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by avoiding potentially erroneous inputs fortrying to initiate finding another component of the associatedcomponents), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the separation alert includes a representation of amap and a visual indication of the remote locator object displayed at alocation on the representation of the map that corresponds to thelocation of the remote locator object (920 a), such as therepresentation of Object on map 810 in separation alert 808 in FIG. 8B(e.g., the notification that the remote locator object has beenseparated from the user includes a map and a representation (e.g., icon,image, etc.) of the remote locator object at a location on the mapcorresponding to the current location and/or last known location of theremote locator object). The above-described manner of displaying a mapin the separation alerts provides a quick and efficient manner ofindicating the location of the remote locator object, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., without requiring separate input forviewing information about the location of the remote locator object),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the separation alert includes a selectable optionthat is selectable to display a user interface associated with theremote locator object, wherein the user interface associated with theremote locator object includes additional information for locating theremote locator object (922 a), such as selectable option 812 a in FIG.8M (e.g., the notification includes a button and/or the notificationitself is selectable to display a user interface associated with theremote locator object). In some embodiments, the user interfaceassociated with the remote locator object includes information about theremote locator object and optionally includes selectable options toperform one or more functions associated with the remote locator object,including an option that is selectable to find the remote locator object(e.g., display navigation instructions or directions to reach thelocation of the remote locator object). The above-described manner ofincluding the selectable option in the separation alert provides a quickand efficient manner of accessing a user interface associated with theremote locator object, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byavoiding potentially erroneous input for accessing the user interfaceassociated with the remote locator object), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the user interface associated with the remotelocator object includes a visual indication that indicates a location atwhich the remote locator object was separated from the location of theuser, and the visual indication is selectable to initiate a process todesignate the location at which the remote locator object was separatedfrom the location of the user as a trusted location for the remotelocator object (924 a), such as indication 836 in FIG. 8N (e.g., theuser interface associated with the remote locator object includes anindication of the current location of the remote locator object and/orthe last known location of the remote locator object. For example, theuser interface includes the address (e.g., or nearest address) of theremote locator object or the name of the location of the remote locatorobject (e.g., name of the business, landmark, etc.). In someembodiments, the user interface includes a selectable option that isselectable to add the current location of the remote locator object(e.g., or last known location of the remote locator object) as a trustedlocation (e.g., a location at which separation alerts are not triggeredif a separation alert would otherwise be generated (e.g., if any of theseparation criteria are satisfied), except that the remote locatorobject is within a threshold radius/distance of the trusted location(e.g., within 6 inches, 1 foot, 3 feet, 20 feet, 100 feet, etc.)) suchthat future separation alerts are not generated if the remote locatorobject is at the same location.). The above-described manner ofincluding the selectable option in the user interface associated withthe remote locator object provides a quick and efficient manner ofdesignating the current location of the remote locator object as atrusted location, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byavoiding potentially erroneous input for designating the currentlocation of the remote locator object as a trusted location), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, in accordance with a determination that one or morecriteria are satisfied (e.g., the electronic device and/or remotelocator object were not moving together when the remote locator objectwas determined to be separated from the electronic device, such asdescribed earlier with reference to the second separation criteria), theseparation alert includes a selectable option that is selectable toinitiate a process to designate the location of the remote locatorobject as a trusted location for the remote locator object (926 a), suchas selectable option 812 b in FIG. 8B (e.g., the separation alertincludes an option to designate the current location of the remotelocator object (e.g., or the last known location of the remote locatorobject) as a trusted location (e.g., a location at which separationalerts are not triggered if a separation alert would otherwise begenerated (e.g., if any of the separation criteria are satisfied),except that the remote locator object is within a thresholdradius/distance of the trusted location (e.g., within 6 inches, 1 foot,3 feet, 20 feet, 100 feet, etc.))). In some embodiments, the one or morecriteria are satisfied if the separation alert is generated because theuser moved away from the location of the remote locator object (e.g.,and the remote locator object remained stationary). In some embodiments,if the one or more criteria are not satisfied (e.g., if the userremained stationary and the remote locator object moved away from thelocation of the user), the notification does not include the selectableoption. The above-described manner of including the selectable option inthe separation alert provides a quick and efficient manner ofdesignating the current location of the remote locator object as atrusted location, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byavoiding potentially erroneous input for designating the currentlocation of the remote locator object as a trusted location), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the process to designate the location of the remotelocator object as a trusted location for the remote locator objectincludes (928 a), in accordance with a determination that the remotelocator object has been separated from the location of the user at thelocation of the remote locator object without a respective set of one ormore other remote locator objects being separated from the location ofthe user at the location of the remote locator object, designating thelocation of the remote locator object as a trusted location for theremote locator object without designating the location of the remotelocator object as a trusted location for other remote locator objects inthe respective set of one or more other remote locator objects (928 b),such as selectable option 812 b in FIG. 8J-1 being selectable todesignate the current location of Object 1 as a trusted location forObject 1 without designating that location a trusted location for Object2 (e.g., if the separation alert is associated with one remote locatorobject that separated from the user, then selecting the option todesignate the current location of the remote locator object as a trustedlocation causes the current location of the remote locator object to beadded as a trusted location for the remote locator object, but does notcause the current location of the remote locator object to be added as atrusted location for other remote locator objects associated with theelectronic device (e.g., remote locator objects that remain with theelectronic device/user).). The above-described manner of including theselectable option for this remote locator object but not others in theseparation alert provides a quick and efficient manner of designatingthe current location of the remote locator object as a trusted location,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., by avoiding potentiallyerroneous input for designating the current location of the remotelocator object as a trusted location), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, the process to designate the location of the remotelocator object as a trusted location for the remote locator objectincludes (930 a), in accordance with a determination that the remotelocator object (e.g., a first remote locator object) and a second remotelocator object (different from the first remote locator object) havebeen separated from the location of the user at the location of theremote locator object (930 b) (e.g., if two remote locator objects havebeen separated from the user (e.g., both remote locator objectsindividually satisfy either the first or the second separation criteria)and the two remote locator objects are together and/or optionally withina threshold distance from each other (e.g., within 1 foot, 3 feet, 20feet, at the same location, at the same business, at the same landmark,etc.).), designating (930 c) the location of the remote locator objectas a trusted location for the remote locator object (e.g., selecting theoption on the separation alert to designate the current location as atrusted location causes the current location of the remote locatorobject to be added as a trusted location for the remote locator object),and designating (930 d) the location of the remote locator object as atrusted location for the second remote locator object, such asselectable option 812 b in FIG. 8I being selectable to designate thecurrent location of Objects 1 and 2 as a trusted location for Objects 1and 2 (e.g., selecting the option on the separation alert to designatethe current location as a trusted location causes the current locationof the remote locator object to be added as a trusted location for boththe remote locator object and the second remote locator object). Forexample, one separation alert is generated for the separation of boththe remote locator object and the second remote locator object, and thussetting the current location as the trusted location applies to both theremote locator object and the second locator object. In someembodiments, if a third remote locator object is with the remote locatorobject and second locator object and also satisfies the separationcriteria, the location of the remote locator object is also added as atrusted location for the third remote locator object. However, if thethird remote locator object is with the remote locator object and thesecond locator object, but does not satisfy the separation criteria, thelocation optionally is not added as a trusted location for the thirdremote locator object (e.g., the separation alert is not associated withthe third remote locator object). The above-described manner ofincluding the selectable option for a plurality of remote locatorobjects provides a quick and efficient manner of designating the currentlocation of the remote locator object as a trusted location for multipleremote locator objects that have been separated from the electronicdevice, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by avoidingthe need for multiple inputs to designate individual trusted locationsfor each of the multiple remote locator objects), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, designating the location of the remote locatorobject as a trusted location for the remote locator object does notdesignate the location of the remote locator object as a trustedlocation for one or more other remote locator objects that are notseparated from the location of the user (932 a), such as Object 2 inFIG. 8J-1 (e.g., in response to selecting the option to designate thecurrent location as a trusted location, the location of the remotelocator object is not added as a trusted location for other remotelocator objects that are with the user, are not with the user, and/orare otherwise being tracked by the electronic device, which do notsatisfy the separation criteria). Thus, in some embodiments, aseparation alert is associated with remote locator object(s) thatsatisfy the separation criteria such that interacting with theseparation alert (e.g., such as by selecting the option on theseparation alert for designating the location of the object as a trustedlocation) performs functions for the associated remote locator object(s)(e.g., the objects that triggered the separation alert), but does notperform functions for remote locator object(s) not associated with theseparation alert (e.g., objects that did not trigger the separationalert). Thus, even if a given location is designated as a trustedlocation for a first remote locator object (e.g., thus causing thedevice to not generate separation alerts if the first remote locatorobject is separated from the electronic device while the first remotelocator object is at the given location), it is not designated as atrusted location for a second remote locator object (e.g., thus stillcausing the device to generate separation alerts if the second remotelocator object is separated from the electronic device while the secondremote locator object is at the given location). The above-describedmanner of designated independent trusted locations for different remotelocator objects provides for flexible and robust designation of trustedlocations for different remote locator objects, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by avoiding overly broad designations of trustedlocations), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the one or more criteria include a criterion thatis satisfied when the separation alert was generated in accordance withthe determination that the second separation criteria are met, and isnot satisfied when the separation alert was generated in accordance withthe determination that the first separation criteria are met (934 a),such indicated by separation alert 808 in FIG. 8A including selectableoption 812 b for designating the current location of Object as a trustedlocation for Object (e.g., the separation alert includes the selectableoption to designate the current location (e.g., or last known location)of the remote locator object if the criteria that triggered theseparation alert is that remote locator object has remained stationary(e.g., or moved less than the threshold amount) while the user movedaway from the remote locator object). In some embodiments, in accordancewith a determination that the one or more criteria are not satisfied,the separation alert does not include the selectable option that isselectable to initiate the process to designate the location of theremote locator object as a trusted location for the remote locatorobject (934 b), such as separation alert 808 in FIG. 8C not includingselectable option 812 b for designating the current location of Objectas a trusted location for Object (e.g., if the separation alert wastriggered while either the remote locator object or the user are inmotion (e.g., not stationary), then the separation alert does notinclude the option to designate the current location of the remotelocator object as a trusted location). In some embodiments, the optionis not provided because a fixed location is not able to be determined asa result of the remote locator object being in motion. In someembodiments, if the separation alert was triggered due to the firstseparation criteria being satisfied and it is determined that the remotelocator object is with another user (e.g., following the location ofanother user), then the separation alert optionally includes an optionto designate the other user as a trusted user. In some embodiments, atrusted user acts like a moving trusted location such that if the remotelocator object would otherwise trigger a separation alert, but isdetermined to be in the possession of or with (e.g., within a thresholddistance of, such as 1, 2, 3, 5, 10, 15 feet of) a trusted user, aseparation alert is not generated. The above-described manner ofselectively including the selection option in the separation alertensures that a process for designated a trusted location based on thelocation of the remote locator object is not initiated when the locationof the remote locator object may not be suitable for doing so, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by avoiding erroneousdesignation of trusted locations, which then requires further input forcorrection), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the separation alert includes a selectable optionthat is selectable to initiate a process to disable separation alertsfor the remote locator object (936 a), such as selectable option 812 cin FIGS. 8B-8C (e.g., the separation alert includes a selectable optionto disable future separation alerts for the remote locator object thattriggered the separation alert (e.g., without designating the currentlocation of the remote locator object as a trusted location for theremote locator object)). In some embodiments, in response to detectingselection of the selectable option, the electronic device disablesseparate alerts for the remote locator object such that futureseparations of the remote locator object from the electronic device(e.g., in accordance with the first or second separation criteria) willnot cause the electronic device to generate a separation alert for theremote locator object. In some embodiments, if the separation alert isassociated with multiple remote locator objects (e.g., if multipleremote locator objects are with each other or near each other and/orsatisfy the separation criteria), the selectable option is selectable todisable future separation alerts for the multiple remote locatorobjects. The above-described manner of including the selection option inthe separation alert provides a quick and efficient manner of disablingseparation alerts for a given remote locator object, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by avoiding the need for additional,potentially erroneous inputs, for disabling separation alerts for thisremote locator object, optionally without doing so for other remotelocator objects), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, displaying the separation alert includes (938 a),in accordance with a determination that one or more criteria aresatisfied, wherein whether the one or more criteria are satisfied isbased on a number of times the remote locator object has been separatedfrom the location of the user, displaying the separation alertconcurrently with one or more options for adjusting separation alertsettings for the remote locator object (938 b), such as options 812 band/or 812 c in FIG. 8B (e.g., the separation alert includes selectableoptions, such as an option to set the location of the remote locatorobject as a trusted location and/or an option to disable futureseparation alerts for the remote locator object, if the separation alerthas not been generated or the first/second separation criteria have notbeen satisfied for the remote locator object more than a thresholdnumber of times (e.g., 1 time, 3 times, 5 times, 10 times, 50 times, 100times, etc.)). In some embodiments, the number of times that aseparation alert has been generated is unique for each remote locatorobject (e.g., each remote locator object has an associated counter thattracks the number of times separation alerts have been generated and/orthe first/second separation criteria have been satisfied) or the numberof times that a separation alert has been generated is unique for theuser (e.g., separation alerts and/or satisfaction of the first/secondseparation criteria, optionally triggered by any remote locator objectand optionally displayed on any of the user's devices, are tracked todetermine how many separation alerts have been generated and/or thefirst/second separation criteria have been satisfied), or the number oftimes that a separation alert has been generated is unique to theelectronic device (e.g., without regard to the number of separationalerts that are generated on other devices that are associated with theuser).

In some embodiments, in accordance with a determination that the one ormore criteria are not satisfied, displaying the separation alert withoutdisplaying the one or more options for adjusting the separation alertsettings for the remote locator object (938 c), such as separation alert808 in FIG. 8D not includes options 812 b and/or 812 c (e.g., if morethan the threshold number of separations have been generated (e.g.,unique for the remote locator object, unique for the device, and/orunique for the user, as described above), then the separation alert doesnot include the one or more options). In some embodiments, even if theseparation alert does not include the one or more options, theseparation alert is selectable to display a user interface associatedwith the remote locator object(s) that triggered the alert, whichincludes options to perform the functions associated with the one ormore options that are no longer included on the separation alert. Forexample, the user is able to select the separation alert to display auser interface associated with the remote locator object and from theuser interface, select an option to designate a new trusted location forthe remote locator object or to silence and/or disable future separationalerts for the remote locator object. The above-described manner ofselectively including the selectable option(s) in the separation alertprovides a quick and efficient manner of facilitating separation alertsettings changes while avoiding unnecessary use of resources forincluding the selectable options when they are likely not needed, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by avoiding accidentalchanges of separation alert settings when those settings have not beenaccessed via the separation alert previously), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the electronic device displays (940 a), via theoutput component, a user interface for designating one or more locationsas trusted locations for the remote locator object, such as userinterface 846 in FIG. 8S (e.g., a user interface that allows a user toset certain geographic locations as trusted locations for the remotelocator object). In some embodiments, the user interface includes a listof locations that have already been set as trusted locations (e.g., forthe remote locator object or other remote locator objects), whichoptionally are able to be toggled on or off. In some embodiments, theuser interface includes an option to add a new location as a trustedlocation. In some embodiments, in accordance with a determination that arespective location has been designated as a trusted location foranother remote locator object associated with the electronic device butnot the remote locator object, the user interface includes a selectableoption that is selectable to designate the respective location as atrusted location for the remote locator object (940 b), such asselectable options 852, 854, 856 in FIG. 8S, (e.g., the user interfaceincludes one or more suggestions of possible locations that have beendesignated as trusted locations for other remote locator objects orother devices. In some embodiments, the suggestions are selectable toadd the respective location as a trusted location for the remote locatorobject.). In some embodiments, in accordance with a determination thatthe respective location has not been designated as a trusted locationfor another remote locator object associated with the electronic device,the user interface does not include the selectable option that isselectable to designate the respective location as a trusted locationfor the remote locator object (940 c), such as a location not appearingunder “Suggestions” in FIG. 8S if that location is not designated as atrusted location for a remote locator object (e.g., if a given locationhas not been designated as a trusted location for another remote locatorobject, the user interface does not include the suggestion of the givenlocation as a trusted location for the remote locator object). In someembodiments, the user interface includes smart suggestions based on theuser's and/or electronic device's location history and/or travelhistory. For example, the user interface includes a suggestion to addthe user's work or home address as a trusted location (e.g., if, forexample, the user's work or home address has not yet been added as atrusted location). The above-described manner of suggesting trustedlocations provides a quick and efficient manner of setting trustedlocations for the remote locator object that are likely candidates forbeing trusted locations, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by avoiding the need for extra, potentially erroneous input, forfinding and/or designating previously-designated trusted locations astrusted locations for the remote locator object), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, displaying the user interface for designating theone or more locations as trusted locations for the remote locator objectincludes (942 a), in accordance with the determination that therespective location has been designated as a trusted location foranother remote locator object associated with the electronic device butnot the remote locator object, displaying, in the user interface, avisual indication of an identity of a second remote locator object forwhich the respective location has been designated as a trusted location(942 b), such as the identifications of “Object 2” and “Device 3” forthe “Office” suggested location in FIG. 8S (e.g., the suggestedlocations includes an indication of the names of the items and/or remotelocator objects that have the respective suggested location as a trustedlocation). For example, a respective suggested location includes atextual indication that it is a “trusted location for ‘Keys’”. In someembodiments, the respective suggested location additionally oralternatively includes an indication of the number of remote locatorobjects for which the respective suggested location has been designatedas a trusted location. The above-described manner of indicatinginformation about the other remote locator objects with which thesuggested trusted location is associated provides a quick and efficientmanner of conveying relevant information about the suggested trustedlocation, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by conveyinginformation that confirms whether the suggested location should bedesignated as a trusted location for the remote locator object based onits relationship with the other items for which the suggested locationis designated a trusted location), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, displaying the user interface for designating theone or more locations as trusted locations for the remote locator objectincludes (944 a), in accordance with the determination that therespective location has been designated as a trusted location foranother remote locator object associated with the electronic device butnot the remote locator object, displaying, in the user interface, avisual indication of a number of other remote locator objects associatedwith the electronic device for which the respective location has beendesignated as a trusted location (944 b), such as the indication of“Used by 5 other objects” for the “Gym” suggested location in FIG. 8S(e.g., the suggested locations includes an indication of how many itemshave the respective suggested location as a trusted location. Forexample, a respective suggested location includes a textual indicationthat it is “used by two other devices”.). The above-described manner ofindicating information about the other remote locator objects with whichthe suggested trusted location is associated provides a quick andefficient manner of conveying relevant information about the suggestedtrusted location, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byconveying information that confirms whether the suggested locationshould be designated as a trusted location for the remote locator objectbased on how many other items are using that suggested location as atrusted location), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, the first separation criteria and the secondseparation criteria include a criterion that is satisfied when, prior togenerating the separation alert, the location associated with the userand the location of the remote locator object exited a trusted locationtogether, and is not satisfied when, prior to generating the separationalert, the location associated with the user and the location of theremote locator object did not exit a trusted location together (946 a),such as described with reference to trusted location 814 in FIGS. 8E-8F(e.g., separation alerts are enabled to be generated if the remotelocator object and the user were together at some point in the past(e.g., optionally for more than a threshold amount of time, such as 10minutes, 1 hour, 4 hours, 8 hours, 12 hours, etc., and/or optionallywithin a last threshold amount of time, such as 10 minutes, 1 hour, 4hours, 8 hours, 12 hours, etc.)). In some embodiments, separation alertsare enabled to be generated if the remote locator object and the userwere both located at a trusted location (e.g., home, work, etc.) andleft the trusted location together (e.g., or within a threshold distancefrom each other, such as 1 foot, 3 feet, 10 feet, 20 feet, etc.). Insome embodiments, separation alerts are enabled to be generated once aday (or any other period of time, such as for every 12 hour period, forevery 24 hour period, for every 1-week period, etc.). For example, ifthe user leaves home with a remote locator object and at some pointlater in the day, is separated from the remote locator object, aseparation alert is generated. However, if the user leaves anotherlocation (e.g., leaves a non-trusted location in the morning) with theremote locator object (e.g., without having been with the remote locatorobject in a trusted location earlier that day), then separation alertsare not subsequently generated for the remote locator object (e.g., forthe remainder of the day, until the user/device and the remote locatorobject return together to a trusted location), even if the separationcriteria are otherwise satisfied (e.g., even if the user/device becomesseparated from the remote locator object). In some embodiments, whetherseparation alerts are generated for the remote locator object is resetevery time the user returns to a trusted location and/or resets once aday such that the user must then exit the trusted location with theremote locator object to re-enable separation alerts. In someembodiments, requiring separation alerts to be enabled for the day(e.g., by requiring the user and the remote locator object be in thesame trusted location and leave the trusted location together)automatically disables separation alerts for remote locator objects ininstances when the remote locator object(s) are likely intentionallyleft behind. The above-described manner of selectively enablingseparation alerts for a remote locator object based on whether thedevice and the remote locator object were together in a trusted locationensures that unnecessary separation alerts are not generated, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by avoiding consumption ofresources for generating a separation alert in circumstances whereleaving the remote locator object behind intentionally is more likely),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first separation criteria and the secondseparation criteria include a criterion that is satisfied when at leastone trusted location has been designated for the remote locator object,and is not satisfied when at least one trusted location has not beendesignated for the remote locator object (948 a), such as described withreference to trusted location 816 in FIGS. 8E-8F (e.g., if no trustedlocation has yet been defined for the remote locator object, then do notgenerate separation alerts even if separation alerts would otherwise begenerated). In some embodiments, defining a trusted location (e.g.,home, work, etc.) for a remote locator object allows the device todetermine whether the remote locator object and the user left thetrusted location together, which is optionally a requirement forenabling separation alerts (e.g., for the day). The above-describedmanner of selectively enabling separation alerts for a remote locatorobject based on whether a trusted location has been designated for theremote locator object ensures that unnecessary separation alerts are notgenerated, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by avoidingconsumption of resources for generating a separation alert incircumstances where leaving the remote locator object behindintentionally is more likely), which additionally reduces power usageand improves battery life of the electronic device by enabling the userto use the electronic device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 9A-9J have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700, 1100, 1300 and 1500) are also applicable in an analogousmanner to method 900 described above with respect to FIGS. 9A-9J. Forexample, presenting separation notifications described above withreference to method 900 optionally has one or more of thecharacteristics of locating objects or receiving notifications aboutobject status or separation, etc., described herein with reference toother methods described herein (e.g., methods 700, 1100, 1300 and 1500).For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A-1B, 3, 5A-5H) orapplication specific chips. Further, the operations described above withreference to FIGS. 9A-9J are, optionally, implemented by componentsdepicted in FIGS. 1A-1B. For example, detecting operation 902 a andgenerating operations 902 c and 902 d are optionally, implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch screen 504,and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch screen corresponds to a predefined event or sub-event, such asselection of an object on a user interface. When a respective predefinedevent or sub-event is detected, event recognizer 180 activates an eventhandler 190 associated with the detection of the event or sub-event.Event handler 190 optionally utilizes or calls data updater 176 orobject updater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

Locator Processes for a Device or a Remote Locator Object

Users interact with electronic devices in many different manners. Insome embodiments, an electronic device or a remote locator object isable to report its location to an electronic device in different ways(e.g., using different locator processes). For example, a first deviceor remote locator object may be compatible with a first locator process(e.g., based on ultra-wideband radio technology), while a second deviceor remote locator object may be compatible with a second locator process(e.g., based on Bluetooth communication technology) but not the firstlocator process. The embodiments described below provide ways in whichan electronic device utilizes a first or second locator process forlocating a device or a remote locator object based on the device orremote locator object being located, thus enhancing the user'sinteractions with the electronic device. Enhancing interactions with adevice reduces the amount of time needed by a user to performoperations, and thus reduces the power usage of the device and increasesbattery life for battery-powered devices. It is understood that peopleuse devices. When a person uses a device, that person is optionallyreferred to as a user of the device.

FIGS. 10A-10T illustrate exemplary ways in which an electronic deviceutilizes a first or second locator process for locating a device or aremote locator object based on the device or remote locator object beinglocated in accordance with some embodiments of the disclosure. Theembodiments in these figures are used to illustrate the processesdescribed below, including the processes described with reference toFIGS. 11A-11F.

As will be described below, FIGS. 10A-10T illustrate two differentlocator processes being utilized by device 500 to locate a first or asecond object. The first object (“Object 1”) is compatible with thefirst locator process (e.g., because Object 1 and/or device 500 includecircuitry or other components for utilizing the first locator process),and the second object (“Object 2”) is compatible with the second locatorprocess, but not the first locator process (e.g., because Object 2and/or device 500 do not include circuitry or other components forutilizing the first locator process, but do include circuitry or othercomponents for utilizing the second locator process). In someembodiments, the first locator process is able to determine the distancebetween device 500 and Object 1 and the directional position of Object 1relative to device (e.g., straight ahead, to the left, to the right,behind, etc.). For example, the first locator process includes utilizingthe Angle of Arrival (AoA) and/or the Angle of Departure (AoD) featuresof Bluetooth 5.0 and/or features of ultra-wideband radio technology. Insome embodiments, the second locator process is able to determine adistance between device 500 and Object 2, but is not able to determinethe directional position of Object 2 relative to device 500. Further, insome embodiments, the distance determination of the second locatorprocess is less accurate than the distance determination of the firstlocator process. While description of FIGS. 10A-10T is provided in thecontext of device 500 locating “objects” (e.g., remote locator objects,as described in this disclosure), it is understood that the features ofthe embodiments described with reference to FIGS. 10A-10T applyanalogously to the context of device 500 locating other electronicdevices (e.g., earbuds, smart watches, tablet computers, etc.).

FIGS. 10A-10B illustrate an exemplary device 500 (e.g., at differenttimes) that includes touch screen 504. In FIGS. 10A-10B, device 500 isdisplaying user interface 1002, which is optionally a user interface ofan object and/or device location tracking application installed ondevice 500. User interface 1002 includes a representation of a map, arepresentation 1006 of the current location of device 500 on therepresentation of the map (e.g., at a location on the map correspondingto the physical location of device 500 determined using a GPS sensor ondevice 500, for example), a representation (e.g., icon) 1004 acorresponding to Object 1 at a location on the representation of the mapcorresponding to the last known location of Object 1, and arepresentation (e.g., icon) 1004 b at a location on the representationof the map corresponding to the last known location of Object 2. In FIG.10A, user interface 1002 includes user interface element 1008 acorresponding to Object 1, and including a selectable option 1010 a thatis selectable to initiate a locator process for locating Object 1.Similarly, in FIG. 10B, user interface 1002 includes user interfaceelement 1008 b corresponding to Object 2, and including a selectableoption 1010 b that is selectable to initiate a locator process forlocating Object 2. As previously described, Object 1 is optionallycompatible with the first locator process mentioned earlier, and Object2 is optionally compatible with the second locator process mentionedearlier, but not the first locator process mentioned earlier. In someembodiments, both the first and the second locator processes are locatorprocesses used by device 500 when the object being located is relativelyclose to device 500 (e.g., within 15, 25, 50, 75, 100, 200, 400 feet ofdevice 500). In some embodiments, if the object being located isrelatively far from device 500 (e.g., greater than 500 feet away),device 500 optionally utilizes a different, third locator process thatincludes displaying, on the map in user interface 1002,walking/cycling/driving directions to the object being located (e.g., asdescribed with reference to method 1300)—Objects 1 and 2 are optionallyequally compatible with the third locator process.

In FIGS. 10C-10D, device 500 detects selection of selectable options1010 a and 1010 b (e.g., via tap of contact 1003), respectively, forinitiating locator processes for locating Objects 1 and 2, respectively.Because Objects 1 and 2 are relatively close to device 500, device 500initiates the first or second locator processes described above.Further, because Object 1 is compatible with the first locator process,device 500 initiates the first locator process for locating Object 1, asshown in FIG. 10E. Analogously, because Object 2 is compatible with thesecond locator process but not the first locator process, device 500initiates the second locator process for locating Object 2, as shown inFIG. 10F.

As shown in FIG. 10E, Object 1 is 30 feet to the right of device 500,and the first locator process optionally starts with a user interface1012 a that indicates 1018 a that device 500 needs to be moved (e.g.,closer to Object 1) for the first locator process to continue. In someembodiments, the first locator process (e.g., based on ultra-widebandradio technology communication between device 500 and Object 1) requiresa minimum signal strength or signal-to-noise ratio to be able to providedistance and/or directionality information for locating Object 1. Userinterface 1012 a in FIG. 10E optionally includes dots 1016 a that movearound user interface 1012 a (e.g., and does not include distance and/ordirectionality information for locating Object 1) until device 500 ismoved close enough to Object 1 for the first locator process tocontinue.

As shown in FIG. 10F, Object 2 is 30 feet to the right of device 500,and the second locator process also optionally starts with a userinterface 1012 b that indicates 1018 b that device 500 needs to be moved(e.g., closer to Object 2) for the second locator process to continue.In some embodiments, the second locator process (e.g., based onBluetooth communication between device 500 and Object 2) requires aminimum signal strength or signal-to-noise ratio to be able to providedistance information for locating Object 2. User interface 1012 b inFIG. 10F optionally also includes dots 1016 b that move around userinterface 1012 b (e.g., and does not include distance information forlocating Object 2) until device 500 is moved close enough to Object 2for the second locator process to continue. User interfaces 1012 a and1012 b also both include selectable options 1020 a and 1020b, which areselectable to exit the first and second locator processes, respectively(e.g., and return to the user interfaces of FIGS. 10A-10D), andselectable options 1022 a and 1022 b, which are selectable to causeObjects 1 and 2, respectively, to emit audible sounds. Therefore, insome embodiments, the first locator process and the second locatorprocess both start with the same user interface 1012 a/1012 b.

In FIGS. 10G-10H, device 500 and/or Objects 1 or 2 have moved such thatObjects 1 and 2 are now 20 feet to the right of device 500, whichoptionally provides sufficient signal for the first and second locatorprocesses to continue. In response, in FIG. 10G in which device 500 isutilizing the first locator process to locate Object 1, device 500updates user interface 1012 a to include directional indication 1024 anddistance/direction indication 1026 a. Directional indication 1024graphically indicates the relative direction of Object 1 relative todevice 500 (e.g., an arrow pointing towards Object 1).Distance/direction indication 1026 a textually indicates the distancebetween device 500 and Object 1 (e.g., “20 ft.”), and optionally alsoindicates the relative direction of Object 1 relative to device 500(e.g., “to the right”). Directional indication 1024 is optionallyupdated by device 500 in real-time as the relative direction of Object 1changes (e.g., due to positional or orientational movement of device 500and/or Object 1). Further, distance/direction indication 1026 a is alsooptionally updated by device 500 in real-time as the distance and/orrelative direction of Object 1 changes (e.g., due to positional ororientational movement of device 500 and/or Object 1). For example, ifObject 1 changes to being 19 feet from device 500, device 500 wouldoptionally update indication 1026 a to indicate “19 ft. to the right”.

In FIG. 10H in which device 500 is utilizing the second locator processto locate Object 2, device 500 updates user interface 1012 b to includedistance indication 1026 b, and user interface 1012 b does not include adirectional indication of Object 2 relative to device 500 (e.g., becausethe second locator process is not able to determine the relativedirection of Object 2 relative to device 500). Distance indication 1026b is optionally an indication that provides a coarse indication of thedistance between device 500 and Object 2 (e.g., corresponding to and/orindicating ranges of distance between device 500 and Object 2), ratherthan a direct indication of the distance between device 500 and Object 2(e.g., such as in user interface 1012 a in FIG. 10G). For example, inFIG. 10H, Object 2 is 20 feet to the right of device 500. As a result,device 500 displays distance indication 1026 b that indicates thatObject 2 is “Far” from device 500, which optionally corresponds toObject 2 being 15-25 feet from device 500, but does display anindication of 20 feet in user interface 1012 b. In some embodiments,indication 1026 b is a less precise indication of distance as comparedwith indication 1026 a in user interface 1012 a. Device 500 optionallydisplays the distance range of 15-25 feet corresponding to “Far” in userinterface 1012 b, and optionally does not display the distance range of15-25 feet in user interface 1012 b. In contrast to indications 1024 and1026 a in user interface 1012 a, indication 1026 b optionally does notupdate in response to any change in distance between device 500 andObject 2, because indication 1026 b optionally corresponds to a range ofdistances rather than a singular or direct distance between device 500and Object 2. For example, if Object 2 were to move to being 19 feetfrom device 500, device 500 would optionally leave indication 1026 bunchanged in user interface 1012 b, because indication 1026 b (“Far”)optionally corresponds to a range of distances (e.g., 15-25 feet) thatincludes the original and the updated distance between device 500 andObject 2. Therefore, in some embodiments, once the object being locatedis within a threshold distance of device 500 (e.g., within 20 or 25 feetof device 500), the user interfaces of the first and second locatorprocesses diverge as described.

In FIGS. 10I-10J, device 500 and/or Objects 1 or 2 have moved such thatObjects 1 and 2 are now 10 feet to the left of device 500. In response,in FIG. 10I in which device 500 is utilizing the first locator processto locate Object 1, device 500 updates directional indication 1024(e.g., to be pointed towards the left) and distance/direction indication1026 a to indicate that Object 1 is 10 feet to the left of device 500.As described previously, directional indication 1024 is optionallyupdated by device 500 in real-time as the relative direction of Object 1changes (e.g., due to positional or orientational movement of device 500and/or Object 1). Further, distance/direction indication 1026 a is alsooptionally updated by device 500 in real-time as the distance and/orrelative direction of Object 1 changes (e.g., due to positional ororientational movement of device 500 and/or Object 1).

In FIG. 10J in which device 500 is utilizing the second locator processto locate Object 2, because Object 2 is now no longer within the “Far”range of distances of 15-25 feet, but is now within the “Closer” rangeof distances of 8-15 feet, device 500 updates distance indication 1026 bto indicate “Closer” (which corresponds to the range of distances of8-15 feet)—user interface 1012 b continues to not include a directionalindication of Object 2 relative to device 500, and continues to notinclude an indication of 10 feet, as described previously, but ratherincludes a less precise indication of distance of Object 2 from device500. Thus, the user interfaces of the first and second locator processescontinue to differ as described.

In FIGS. 10K-10L, device 500 and/or Objects 1 or 2 have moved such thatObjects 1 and 2 are now 5 feet in front of device 500. In response, inFIG. 10K in which device 500 is utilizing the first locator process tolocate Object 1, device 500 updates directional indication 1024 (e.g.,to be pointed straight ahead of device 500) and distance/directionindication 1026 a to indicate that Object 1 is 5 feet in front or aheadof device 500. As described previously, directional indication 1024 isoptionally updated by device 500 in real-time as the relative directionof Object 1 changes (e.g., due to positional or orientational movementof device 500 and/or Object 1). Further, distance/direction indication1026 a is also optionally updated by device 500 in real-time as thedistance and/or relative direction of Object 1 changes (e.g., due topositional or orientational movement of device 500 and/or Object 1).

In FIG. 10L in which device 500 is utilizing the second locator processto locate Object 2, because Object 2 is now no longer within the“Closer” range of distances of 8-15 feet, but is now within the “Nearby”range of distances of 3-8 feet, device 500 updates distance indication1026 b to indicate “Nearby” (which corresponds to the range of distancesof 3-8 feet)—user interface 1012 b continues to not include adirectional indication of Object 2 relative to device 500, and continuesto not include an indication of 5 feet, as described previously, butrather includes a less precise indication of distance of Object 2 fromdevice 500. Thus, the user interfaces of the first and second locatorprocesses continue to differ as described.

In FIGS. 10M-10N, device 500 and/or Objects 1 or 2 have moved such thatObjects 1 and 2 are now 3 feet in front of device 500. In someembodiments, when the object being located is within a thresholddistance (e.g., the same threshold distance for both the first and thesecond locator processes, or a different threshold distance for thefirst and the second locator processes) of device 500, device 500displays a geometric shape on the locator process user interfaces, aswill now be described. In some embodiments, the threshold distance isthree feet from device 500. In some embodiments, the threshold distanceof FIGS. 10M-10N is less than the threshold distance that causes device500 to switch from displaying the user interfaces of FIGS. 10E-10F todisplaying the user interfaces of FIGS. 10G-10H.

In response to Object 1 being within the threshold distance (e.g., 3feet) of device 500, in FIG. 10M in which device 500 is utilizing thefirst locator process to locate Object 1, device updates user interface1012 a to include a geometric shape indicator 1028a. In someembodiments, indicator 1028 a is a circle, a square, a triangle, etc. Insome embodiments, the shape of indicator 1028 a corresponds to the shapeof Object 1 (e.g., the object being located), such that differentobjects being located result in a different shape of indicator 1028 adisplayed by device 500. In some embodiments, indicator 1028 a includesan inner geometric shape (e.g., a filled circle) within a larger outergeometric shape (e.g., an unfilled circle). As Object 1 becomes closerto device 500, device 500 optionally updates display of indicator 1028 asuch that the inner geometric shape remains constant, but the outergeometric shape becomes smaller and smaller until it reaches the innergeometric shape (e.g., when Object 1 is at the same location as device500), as will be described. In FIG. 10M, device 500 also updatesindicator 1026 a to indicate that Object 1 is three feet ahead of device500. Further, device 500 ceases displaying directional indicator 1024that was displayed previously in FIG. 10K, for example.

In response to Object 2 being within the threshold distance (e.g., 3feet) of device 500, in FIG. 10N in which device 500 is utilizing thesecond locator process to locate Object 2, device updates user interface1012 b to include a geometric shape indicator 1028 b. In someembodiments, indicator 1028 b is the same indicator as indicator 1028 ain FIG. 10M, though is optionally updated differently than indicator1028 a in FIG. 10M, as will be described. Indicator 1028 b is optionallya circle, a square, a triangle, etc. In some embodiments, the shape ofindicator 1028 b corresponds to the shape of Object 2 (e.g., the objectbeing located), such that different objects being located result in adifferent shape of indicator 1028 b displayed by device 500. In someembodiments, indicator 1028 b includes an inner geometric shape (e.g., afilled circle) within a larger outer geometric shape (e.g., an unfilledcircle). As Objects 2 becomes closer to device 500—but optionally onlyas it gets closer by certain predetermined intervals of distance, aswill be described—device 500 optionally updates display of indicator1028 b such that the inner geometric shape remains constant, but theouter geometric shape becomes smaller and smaller until it reaches theinner geometric shape (e.g., when Object 2 is at the same location asdevice 500), as will be described. In FIG. 10N, device 500 also updatesindicator 1026 b to indicate that Object 2 is within the “Very Close”range of distances of zero to three feet (e.g., by updating indicator1026 b to indicate “Very Close” (which corresponds to the range ofdistances of zero to three feet)—user interface 1012 b continues to notinclude a directional indication of Object 2 relative to device 500.

In some embodiments, the sizes and/or shapes of indicators 1028 a and1028 b displayed by device 500 in the first and second locatorprocesses, respectively, are the same at the moment they are displayed.For example, upon the object being located being within three feet ofdevice 500 (e.g., the threshold distance at which device 500 switchesfrom displaying the user interfaces of FIGS. 10K-10L to displaying theuser interfaces of FIGS. 10M-10N), device 500 displays the same sizeand/or shape indicator in user interfaces 1012 a and 1012 b in the firstand second locator processes, respectively.

However, as mentioned previously, after indicators 1028 a and 1028 b aredisplayed by device 500, device 500 optionally updates indicators 1028 aand 1028 b differently as a function of the distance between device 500and the object being located depending on which locator process is beingutilized by device 500. For example, in FIGS. 100-10P, device 500 and/orObjects 1 or 2 have moved such that Objects 1 and 2 are now 2 feet infront of device 500. In response, in FIG. 100 in which device 500 isutilizing the first locator process to locate Object 1, device 500updates indicator 1028 a to reduce the size of the outer geometric shape(e.g., while maintaining the size of the inner geometric shape) tocorrespond to a distance of two feet from device 500. Device 500 alsoupdates indicator 1026 a to indicate that Object 1 is now 2 feet infront of device 500.

In contrast, in FIG. 10P in which device 500 is utilizing the secondlocator process to locate Object 2, device 500 does not update indicator1028 b in response to Object 2 moving from three feet away from device500 to two feet away from device 500—device 500 optionally displays theinner and outer geometric shapes of indicator 1028 b at the same size asthey were displayed in FIG. 10N. This is optionally the case because inthe second locator process, distance between the object being locatedand device 500 needs to change by some minimum distance or predefinedinterval(s) of distance(s) before device 500 updates indicator 1028 b.For example, the distance between the object being located and device500 needs to change by two feet to cause device 500 to update indicator1028 b. In some embodiments, the sizes of the geometric shapes ofindicator 1028 b in FIGS. 10N and 10P optionally correspond to Object 2being in the range of two to three feet from device 500—and becauseObject 2 remains within that range of two to three feet from device 500in FIG. 10P, device 500 maintains display of indicator 1028 b at thesame size at which it was displayed in FIG. 10N. In FIG. 10P, device 500also maintains display of indicator 1026 b to indicate “Very Close”(which corresponds to the range of distances of zero to three feet), anduser interface 1012 b continues to not include a directional indicationof Object 2 relative to device 500.

In FIGS. 10Q-10R, device 500 and/or Objects 1 or 2 have moved such thatObjects 1 and 2 are now 1 foot in front of device 500. In response, inFIG. 10Q in which device 500 is utilizing the first locator process tolocate Object 1, device 500 updates indicator 1028 a to again reduce thesize of the outer geometric shape (e.g., while maintaining the size ofthe inner geometric shape) to correspond to a distance of one foot fromdevice 500. Device 500 also updates indicator 1026 a to indicate thatObject 1 is now 1 foot in front of device 500.

In FIG. 10R in which device 500 is utilizing the second locator processto locate Object 2, device 500 also updates indicator 1028 b in responseto Object 2 moving from two feet away from device 500 to one foot awayfrom device 500 by reducing the size of the outer geometric shape (e.g.,while maintaining the size of the inner geometric shape) to correspondto a distance of one foot from device 500. The sizes of the outer andinner geometric shapes of indicator 1028 b in FIG. 10R optionallycorrespond to a distance range of zero to two feet (or just under twofeet) of Object 2 from device 500. Therefore, device 500 optionallyupdates indicator 1028 b to the sizes shown in FIG. 10R in response toObject 2 becoming less than two feet from device 500, and optionallymaintains the sizes of indicator 1028 b until Object 2 is located. Insome embodiments, the sizes of the inner and outer geometric shapes ofindicators 1028 a and 1028 b in FIGS. 10Q-R are the same. In FIG. 10R,device 500 also maintains display of indicator 1026 b to indicate “VeryClose” (which corresponds to the range of distances of zero to threefeet), and user interface 1012 b continues to not include a directionalindication of Object 2 relative to device 500.

In FIGS. 10S-10T, Objects 1 and 2 have been designated as found inresponse to, for example, Objects 1 and 2 changing status (e.g., havingbeen placed in their respective cases, having started charging, havingbeen placed in a user's ear (e.g., if they are earbuds), having beenplaced on a user's wrist (e.g., if they are smart watches), having beenattached to device 500 (e.g., magnetically) if they are attachableaccessories, etc.) and/or being within 0.5, 1, 2, 4, 6, 12 inches ofdevice 500. In FIG. 10S in which device 500 is utilizing the firstlocator process to locate Object 1, in response to Object 1 beingdesignated as found (e.g., in response to changing status), device 500optionally updates indicator 1028 a to only include the inner geometricshape (e.g., at the same size at which it was displayed in FIG. 10Q) andto not include the outer geometric shape, and updates indicator 1030 ato indicate the changed status of Object 1 (e.g., “Found” or “Placed inEar” or “Charging” or “Attached”, etc.). Additionally or alternatively,device 500 updates user interface 1012 a (e.g., the background of userinterface 1012 a) to have a different color than it had before in FIGS.10A-10R, for example. In some embodiments, the background color of userinterface in FIGS. 10A-10R was white, black, or grey, and the backgroundcolor of user interface in FIG. 10S in response to Object 1 beingdesignated as found is green, for example. Indicator 1028 a isoptionally displayed over the current background color in FIGS. 10A-10S.

Device 500 that is utilizing the second locator process optionallyupdates user interface 1012 b similarly or in the same manner as device500 that is utilizing the first locator process. For example, in FIG.10T in which device 500 is utilizing the second locator process tolocate Object 2, in response to Object 2 being designated as found(e.g., in response to changing status), device 500 optionally updatesindicator 1028 b to only include the inner geometric shape (e.g., at thesame size at which it was displayed in FIG. 10R) and to not include theouter geometric shape, and updates indicator 1030 b to indicate thechanged status of Object 2 (e.g., “Found” or “Placed in Ear” or“Charging” or “Attached”, etc.). Additionally or alternatively, device500 updates user interface 1012 b (e.g., the background of userinterface 1012 b) to have a different color than it had before in FIGS.10A-10R, for example. In some embodiments, the background color of userinterface in FIGS. 10A-10R was white, black, or grey, and the backgroundcolor of user interface in FIG. 10T in response to Object 2 beingdesignated as found is green, for example. Indicator 1028 b isoptionally displayed over the current background color in FIGS. 10A-10T.The background color of user interface 1012 a through the various stagesof the first locator process, including the stage at which Object 1 isdesignated as found, is optionally the same as the background color ofuser interface 1012 b through the various stages of the second locatorprocess, including the stage at which Object 2 is designated as found,and are optionally updated in the same way in response to Objects 1 and2 being designated as found in the first and second locator processes.Thus, in some embodiments, the first locator process and the secondlocator process both end with device 500 displaying the same userinterface in both processes in response to the objects being locatedbeing designated as found (e.g., based on a change in status of theobjects being located).

FIGS. 11A-11F are flow diagrams illustrating a method 1100 of utilizinga first or second locator process for locating a device or a remotelocator object based on the device or remote locator object beinglocated in accordance with some embodiments, such as in FIGS. 10A-10T.The method 1100 is optionally performed at an electronic device such asdevice 100, device 300, or device 500 as described above with referenceto FIGS. 1A-1B, 2-3, 4A-4B and 5A-5H. Some operations in method 1100are, optionally combined and/or order of some operations is, optionally,changed.

As described below, the method 1100 provides ways to utilize a first orsecond locator process for locating a device or a remote locator objectbased on the device or remote locator object being located. The methodreduces the cognitive burden on a user when interacting with a userinterface of the device of the disclosure, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, increasing the efficiency of the user's interaction with theuser interface conserves power and increases the time between batterycharges.

In some embodiments, method 1100 is performed at a first electronicdevice (e.g., device 500) in communication with one or more wirelessantenna, a display generation component, and one or more input devices(e.g., a mobile device (e.g., a tablet, a smartphone, a media player, ora wearable device) including wireless communication circuitry,optionally in communication with one or more of a mouse (e.g.,external), trackpad (optionally integrated or external), touchpad(optionally integrated or external), remote control device (e.g.,external), another mobile device (e.g., separate from the electronicdevice), a handheld device (e.g., external), and/or a controller (e.g.,external), etc.). In some embodiments, the display generation componentis a display integrated with the electronic device (optionally a touchscreen display), external display such as a monitor, projector,television, or a hardware component (optionally integrated or external)for projecting a user interface or causing a user interface to bevisible to one or more users, etc.

In some embodiments, the electronic device displays (1102 a), via thedisplay generation component, an information user interface for a secondelectronic device that includes information about the second electronicdevice, such as user interfaces 1008 a and 1008 b in FIGS. 10A-10B(e.g., a map user interface that optionally includes an indication ofthe location of the second electronic device on a map and/or one or moreaffordances for changing settings for the second electronic deviceand/or performing operations associated with the second electronicdevice such as causing the second electronic device to emit a sound, forexample, to assist in finding the second electronic device), includingan option to initiate a finding mode for finding the second electronicdevice, such as options 1010 a and 1010 b in FIGS. 10A-10B (e.g., anaffordance that is selectable to initiate a process to find the secondelectronic device (e.g., similar to a finding user interface asdescribed with reference to method 1300). In some embodiments, thesecond electronic device is a remote locator object, as described abovewith respect to method 900. In some embodiments, the second electronicdevice is a mobile device similar to the first electronic device. Insome embodiments, the second electronic device is any device that isable to gather and provide location information to the first electronicdevice (e.g., directly, via a server, via another electronic device,etc.). In some embodiments, the process for finding the secondelectronic device includes displaying a map user interface optionallywith one or more navigation directions (e.g., driving directions,transit directions, etc.) for navigating to a location associated withthe second electronic device (e.g., the last known location for thesecond electronic device, provided to the first electronic device fromthe second electronic device). In some embodiments, the process forfinding the second electronic device includes displaying a finding userinterface that indicates the distance of the first electronic devicefrom the second electronic device (e.g., 5 feet away, 10 feet away, 20feet away, etc.) and/or the position of the second electronic devicerelative to the first electronic device (e.g., forward, to the left,behind, etc.) (e.g., optionally without providing navigation directionson a map).

In some embodiments, while displaying the information user interface forthe second electronic device, the electronic device receives 1102 b, viathe one or more input devices, a user input corresponding to a requestto initiate the finding mode for the second electronic device, such asselection of options 1010 a and 1010 b in FIGS. 10C-10D (e.g., a tap onthe selectable affordance or a selection input while the selectableaffordance has a focus or a voice input for initiating the finding modefor the second electronic device.

In some embodiments, in response to receiving the user input (1102 c),in accordance with a determination that the second electronic device iscompatible with a first locator process (e.g., if the second electronicdevice has a first set of locator capabilities and/or technology and isable to provide a first set of location information to the firstelectronic device), the electronic device initiates (1102 d) the firstlocator process for finding the second electronic device, such as shownin FIG. 10E with respect to Object 1 (e.g., initiating a method forfinding the second electronic device that optionally takes advantage ofthe ability of the second electronic device to provide information tothe first electronic device such that the first electronic device candetermine both the distance and relative direction of the secondelectronic device compared to the first electronic device). For example,the first locator process is able to determine the distance between thesecond electronic device (e.g., 5 feet away, 10 feet away, 50 feet away,etc.) and the first electronic device and the directional position ofthe second electronic device relative to the first electronic device(e.g., straight ahead, to the left, to the right, behind, etc.). Forexample, the first locator process includes the Angle of Arrival (AoA)and/or the Angle of Departure (AoD) features of Bluetooth 5.0 and/orultra-wide band radio technology) In some embodiments, the first locatorprocess includes displaying both distance information and directioninformation (e.g., optionally concurrently or not concurrently). In someembodiments, using the first locator process provides the firstelectronic device with more accurate distance and/or directioninformation than using the second locator process described below.

In some embodiments, in response to receiving the user input (1102 c),in accordance with a determination that the second electronic device iscompatible with a second locator process and not compatible with thefirst locator process (e.g., the second electronic device has a secondset of locator capabilities and/or technology (e.g., does not includethe first set of locator abilities)) and is able to provide a second setof location information to the first electronic device, but not thefirst set of information to the first electronic device, the electronicdevice initiates (1102 e) the second locator process for finding thesecond electronic device, wherein the second locator process isdifferent from the first locator process, such as shown in FIG. 10F withrespect to Object 2 (e.g., initiating a method for finding the secondelectronic device that takes into account the inability to determine therelative direction of the second electronic device and/or the inabilityto provide the more accurate and/or precise distance and/or directioncapabilities of the first locator process). For example, the secondlocator process is able to determine a distance between the secondelectronic device and the first electronic device, but is not able todetermine the directional position of the second electronic devicerelative to the first electronic device (e.g., the first electronicdevice is able to determine how far away the second electronic deviceis, but not whether the second electronic device is in front, to theleft, behind, to the right, etc. and/or the first electronic device isable to determine distance and/or direction to a lesser degree ofaccuracy and/or precision than with the first locator process). In someembodiments, the second locator process includes displaying the distanceinformation, but does not include displaying direction information.

The above-described manner of initiating a respective locator processfor locating an electronic device (e.g., based on whether the electronicdevice to be found is compatible with a first or second type of locatorprocess) provides a quick and efficient manner of selecting anappropriate locator process for locating the electronic device (e.g.,automatically, based on the capabilities of the electronic device beingfound, without requiring the user to perform additional inputs to selectthe type of locator process), which simplifies the interaction betweenthe user and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient,which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first locator process includes displaying, viathe display generation component, a first user interface having a firstvisual appearance for finding the second electronic device, such as userinterface 1012 a in FIG. 10G, and the second locator process includesdisplaying, via the display generation component, a second userinterface having a second visual appearance, different from the firstvisual appearance, for finding the second electronic device (1104 a),such as user interface 1012 b in FIG. 10H. For example, the first userinterface of the first locator process includes information about therelative location/orientation/direction of the second electronic devicewith respect to the first electronic device and information about adistance between the first electronic device and the second electronicdevice, and the second user interface includes information about thedistance between the first electronic device and the second electronicdevice, but does not include information about the relativelocation/orientation/direction of the second electronic device withrespect to the first electronic device. In some embodiments, the firstuser interface has a different arrangement/structure than the seconduser interface. For example, in some embodiments, the first userinterface includes a visual indication of the relativelocation/orientation/direction of the second electronic device withrespect to the first electronic device in a center region of the userinterface, and a visual indication of the distance between the devicesin an outer region of the user interface, and the second user interfaceincludes a visual indication of the distance between the devices in thecenter region of the user interface. In some embodiments, the visualindications of the distance between the devices are different in thefirst and second user interfaces.

The above-described manner of displaying user interfaces with differentvisual appearances depending on the finding process provides a quick andefficient manner of indicating the finding process that is currently ineffect, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by avoidingerroneous interaction with the device meant for a different findingprocess), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the first locator process includes displaying, viathe display generation component, a visual indication of a location ofthe second electronic device relative to the first electronic devicethat includes an indication of a direction of the second electronicdevice relative to the first electronic device (1106 a), such asindication 1024 in FIG. 10G. For example, during the first locatorprocess, the first electronic device is able to determine the distanceof the second electronic device from the first electronic device anddetermine the relative orientation or direction of the second electronicdevice with respect to the first electronic device (e.g., straightahead, ahead and to the right, to the right, etc.). In some embodiments,during the first locator process, the first electronic device displays auser interface that includes a visual indication of the distance and avisual indication of the relative orientation. For example, the firstlocator process is based on ultra-wideband radio technology.

The above-described manner of indicating the location of the secondelectronic device when the finding process is able to do so provides aquick and efficient manner of providing directions to the secondelectronic device, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byavoiding incorrect movements for finding the second electronic device),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the second locator process does not includedisplaying, via the display generation component, a visual indication ofa location of the second electronic device relative to the firstelectronic device that includes an indication of a direction of thesecond electronic device relative to the first electronic device (1108a), such as user interface 1012 b in FIG. 10H not including anindication of a direction of Object 2 relative to device 500. In someembodiments, during the second locator process, the first electronicdevice is not able to determine the distance of the second electronicdevice from the first electronic device and determine the relativeorientation/direction of the second electronic device with respect tothe first electronic device (e.g., straight ahead, ahead and to theright, to the right, etc.). In some embodiments, during the secondlocator process, the first electronic device is able to determine thedistance of the second electronic device from the first electronicdevice, but is not able to determine the relative orientation/directionof the second electronic device with respect to the first electronicdevice. In some embodiments, the distance determination during thesecond locator process is less accurate/precise than the distancedetermination during the first locator process. In some embodiments, thesecond locator process is based on Bluetooth signal strength between thefirst electronic device and the second electronic device. Thus, in someembodiments, during the second locator process, the first electronicdevice displays indications of ranges of distances between the first andsecond devices (e.g., 10-15 feet, 20-25 feet, 15-30 feet) rather than aprecise indication of the distance between the first and second devices(e.g., 12 feet, 21 feet, 16 feet), and in some embodiments, during thesecond locator process, the first electronic device does not display anindication of a direction (e.g., to the right, straight ahead, to theleft, etc.) of the second electronic device relative to the firstelectronic device.

The above-described manner of not indicating the direction of the secondelectronic device when the finding process is not able to do so ensuresthat erroneous direction information is not displayed, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by avoiding incorrect movements forfinding the second electronic device), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, a beginning of the first locator process and abeginning of the second locator process both include displaying, via thedisplay generation component, a user interface for finding the secondelectronic device that includes a visual indication of a location of thesecond electronic device relative to the first electronic device withoutindicating a direction of the second electronic device relative to thefirst electronic device (1110 a), such as user interfaces 1012 a and1012 b in FIGS. 10E and 10F indicating that the objects being locatedare too far from device 500, without indicating a direction of theobjects being located relative to device 500. For example, at the startof the first locator process (e.g., when the second electronic device istoo far from the first electronic device for its relative location to beaccurately determined, or when the orientation of the first electronicdevice must move through a plurality of orientations to calibrate thelocator process), the first electronic device does not display anindication of the relative direction of the second electronic device. Insome embodiments, the first electronic device displays a user interfacethat indicates a distance of the second electronic device from the firstelectronic device and/or an indication to move/change the orientation ofthe first electronic device through a range of positions/orientations tocalibrate/lock onto the relative location of the second electronicdevice. In some embodiments, the first electronic device displays thesame as described above at the start of the second locator process aswell, despite later stages of the second locator process havingdifferent information/user interfaces, as described above.

The above-described manner of starting both locator processes with thesame/similar displayed information ensures that erroneous locationinformation is not displayed in either process, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by avoiding incorrect movements for finding thesecond electronic device), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, the first locator process and the second locatorprocess both include (1112 a), in accordance with a determination thatthe second electronic device is within a threshold distance (e.g., 0.1,0.5, 1, 2, 3, 5, 10 feet) of the first electronic device, displaying,via the display generation component, a geometric shape, such as shownby indicators 1028 a and 1028 b in FIGS. 10M and 10N, respectively(e.g., that corresponds to a shape of the second electronic device)(1112 b). For example, if the second electronic device is round, thegeometric shape that is displayed is round. In some embodiments, if thesecond electronic device is rectangular, the geometric shape that isdisplayed is rectangular. In some embodiments, the first electronicdevice ceases displaying an indication of the relative location of thesecond electronic device with respect to the first electronic deviceand/or a distance from the second electronic device to the firstelectronic device when it displays the geometric shape.

In some embodiments, the first locator process and the second locatorprocess both include (1112 a), in accordance with a determination thatthe second electronic device is further than the threshold distance fromthe first electronic device, forgoing displaying the geometric shape(1112 c), such as the circular indicators 1028 a and 1028 b in FIGS. 10Mand 10N not being displayed in FIGS. 10K and 10L. For example, until thefirst electronic device is within the threshold distance of the secondelectronic device, the first electronic device does not display thegeometric shape, but instead displays an indication of the relativelocation of the second electronic device with respect to the firstelectronic device and/or a distance from the second electronic device tothe first electronic device.

The above-described manner of displaying a geometric shape when within athreshold distance of the second electronic device provides a quick andefficient manner of indicating that the second electronic device iswithin the threshold distance of the first electronic device, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by avoiding large movementsfor finding the second electronic device when it is within the thresholddistance of the first electronic device), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the first locator process and the second locatorprocess both further include (1114 a), while displaying, via the displaygeneration component, the geometric shape at a first size, detecting achange in distance between the first electronic device and the secondelectronic device (1114 b), such as Objects 1 and 2 getting closer todevice 500 in FIGS. 10M and 10N, respectively (e.g., the firstelectronic device has been moved, by the user, to a greater or lesserdistance from the second electronic device, and/or the second electronicdevice has moved to a greater or lesser distance from the firstelectronic device).

In some embodiments, the first locator process and the second locatorprocess both further include (1114 a), in response to detecting thechange in distance between the first electronic device and the secondelectronic device (1114 c), in accordance with a determination that thedistance between the first electronic device and the second electronicdevice has decreased, updating the geometric shape to be displayed at asecond size, greater than the first size (1114 d), such as circularindicators 1028 a and 1028 b in FIGS. 10M and 10N increasing in size(e.g., once the geometric shape is displayed by the first electronicdevice, as the first and second electronic devices move closer together,the first electronic device increases (or decreases) the size of thegeometric shape to indicate that the second electronic device is gettingcloser to the first electronic device).

In some embodiments, the first locator process and the second locatorprocess both further include (1114 a), in response to detecting thechange in distance between the first electronic device and the secondelectronic device (1114 c), in accordance with a determination that thedistance between the first electronic device and the second electronicdevice has increased, updating the geometric shape to be displayed at athird size, smaller than the first size (1114 e), such as circularindicators 1028 a and 1028 b in FIGS. 10M and 10N decreasing in size(e.g., once the geometric shape is displayed by the first electronicdevice, as the first and second electronic devices move further apart,the first electronic device decreases (or increases) the size of thegeometric shape to indicate that the second electronic device is gettingfurther away from the first electronic device).

The above-described manner of changing the size of the geometric shapeprovides a quick and efficient manner of indicating whether the firstelectronic device is moving closer to or further away from the secondelectronic device, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., byavoiding erroneous movements for finding the second electronic device),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, while displaying, via the display generationcomponent, the geometric shape at a first size (1116 a) (e.g., as partof the first or second locator processes), in accordance with anindication that a distance between the first electronic device and thesecond electronic device has decreased (1116 b) (e.g., the firstelectronic device has been moved, by the user, to a lesser distance fromthe second electronic device, and/or the second electronic device hasmoved to a lesser distance from the first electronic device), inaccordance with a determination that the second locator process forfinding the second electronic device is currently active (1116 c) (e.g.,the second electronic device is compatible with the second locatorprocess but not the first locator process, and therefore the firstelectronic device is performing the second locator process for findingthe second electronic device), in accordance with a determination thatthe decrease in distance between the first electronic device and thesecond electronic device is less than a threshold distance (e.g., 1inch, 2 inches, 6 inches, 12 inches, 24 inches, 36 inches, 48 inches,etc.), display of the geometric shape is maintained at the first size(1116 d), such as indicator 1028 b not changing from FIG. 10N to 10P. Insome embodiments, because the accuracy of the distance determination ofthe second locator process may not be very high, the indication that thedistance between the devices has decreased may have relatively lowprecision. In some embodiments, the indication of the change in distancebetween the two devices is based on a Bluetooth signal strength betweenthe first and second devices increasing (e.g., for the second locatorprocess). In some embodiments, the indication of the change in distancebetween the two devices is based on an ultra-wideband signal between thefirst and second devices (e.g., for the first locator process). In someembodiments, while displaying, via the display generation component, thegeometric shape at a first size (1116 a) (e.g., as part of the first orsecond locator processes), in accordance with an indication that adistance between the first electronic device and the second electronicdevice has decreased (1116 b) (e.g., the first electronic device hasbeen moved, by the user, to a lesser distance from the second electronicdevice, and/or the second electronic device has moved to a lesserdistance from the first electronic device), in accordance with adetermination that the second locator process for finding the secondelectronic device is currently active (1116 c) (e.g., the secondelectronic device is compatible with the second locator process but notthe first locator process, and therefore the first electronic device isperforming the second locator process for finding the second electronicdevice in accordance with a determination that the decrease in distancebetween the first electronic device and the second electronic device isgreater than the threshold distance (e.g., 1 inch, 2 inches, 6 inches,12 inches, 24 inches, 36 inches, 48 inches, etc.), the geometric shapeis updated to be displayed at a second size, greater than the firstsize, such as indicator 1028 b changing from FIG. 10N to 10R (e.g.,because the accuracy of the distance determination of the second locatorprocess may be relatively low or inaccurate, in some embodiments, thefirst electronic device updates the size of the geometric shape insteps, rather than gradually. For example, the first electronic deviceupdates the size of the geometric shape in correspondence with changesin distance between the two devices in steps of 1 inch, 2 inches, 6inches, 12 inches, 24 inches, 36 inches, 48 inches, etc.

In some embodiments, changes in distance that fall within such distancesteps do not result in the geometric shape changing size) (1116 e).

In some embodiments, while displaying, via the display generationcomponent, the geometric shape at a first size (1116 a) (e.g., as partof the first or second locator processes), in accordance with anindication that a distance between the first electronic device and thesecond electronic device has decreased (1116 b) (e.g., the firstelectronic device has been moved, by the user, to a lesser distance fromthe second electronic device, and/or the second electronic device hasmoved to a lesser distance from the first electronic device), inaccordance with a determination that the first locator process forfinding the second electronic device is currently active (e.g., thesecond electronic device is compatible with the first locator process,and therefore the first electronic device is performing the firstlocator process for finding the second electronic device), the geometricshape is updated to be displayed at a third size, greater than the firstsize (e.g., and less than the second size), independent of whether thedecrease in distance between the first electronic device and the secondelectronic device is greater than or less than the threshold distance(1116 f), such as indicator 1028 a changing in both FIGS. 10O and 10Q.For example, because the accuracy of the distance determination of thefirst locator process may be relatively high or accurate, in someembodiments, the first electronic device updates the size of thegeometric shape gradually rather than in steps as the first electronicdevice determines that the distance between the devices has changed,without waiting for the distance change to reach a step or thresholdamount. For example, the first electronic device changes the size of thegeometric shape for every 0.1, 0.2, 0.5, 1, 2, 3 inches of change in thedistance between the first and second electronic devices.

The above-described manner of changing the size of the geometric shapeensures that inaccurate indications of changes in distance are notindicated in the user interface, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by avoiding erroneous movements for finding the secondelectronic device), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In some embodiments, in response to detecting a change in distancebetween the first electronic device and the second electronic device(1118 a) (e.g., the first electronic device has been moved, by the user,to a lesser or greater distance from the second electronic device,and/or the second electronic device has moved to a lesser or greaterdistance from the first electronic device), in accordance with adetermination that the distance between the first electronic device andthe second electronic device is less than a threshold distance (1118 b)(e.g., 10, 20, 40, 50, 100, 200, 300 feet), in accordance with adetermination that the first locator process for finding the secondelectronic device is currently active (e.g., the second electronicdevice is compatible with the first locator process, and therefore thefirst electronic device is performing the first locator process forfinding the second electronic device), a visual indication of a locationof the second electronic device relative to the first electronic devicethat includes an indication of a direction of the second electronicdevice relative to the first electronic device is displayed via thedisplay generation component (1118 c), such as indicator 1024 in FIG.10G (e.g., an indication of the directional position of the secondelectronic device relative to the first electronic device (e.g.,straight ahead, to the left, to the right, behind, etc.)). In someembodiments, an indication of the distance of the second electronicdevice from the first electronic device is displayed (e.g., a textualindication of the distance and/or a graphical indication of thedistance, such as via the size of a displayed geometric shape, aspreviously described). In some embodiments, because the accuracy of thedistance determination of the second locator process may not be veryhigh, the indication that the distance between the devices has changedmay have relatively low precision. In some embodiments, the indicationof the change in distance between the two devices is based on aBluetooth signal strength between the first and second devices changing(e.g., for the second locator process). In some embodiments, theindication of the change in distance between the two devices is based onan ultra-wideband signal between the first and second devices (e.g., forthe first locator process).

In some embodiments, in response to detecting a change in distancebetween the first electronic device and the second electronic device(1118 a) (e.g., the first electronic device has been moved, by the user,to a lesser or greater distance from the second electronic device,and/or the second electronic device has moved to a lesser or greaterdistance from the first electronic device), in accordance with adetermination that the distance between the first electronic device andthe second electronic device is less than a threshold distance (1118 b)(e.g., 10, 20, 40, 50, 100, 200, 300 feet), in accordance with adetermination that the second locator process for finding the secondelectronic device is currently active (e.g., the second electronicdevice is compatible with the second locator process but not the firstlocator process, and therefore the first electronic device is performingthe second locator process for finding the second electronic device), avisual indication of the location of the second electronic devicerelative to the first electronic device that does not include anindication of a direction of the second electronic device relative tothe first electronic device is displayed via the display generationcomponent (1118 d), such as indication 1026 b in FIG. 10H, which doesnot include an indication of a direction of Object 2 relative to device500 (e.g., an indication of the directional position of the secondelectronic device relative to the first electronic device (e.g.,straight ahead, to the left, to the right, behind, etc.) is notdisplayed). In some embodiments, an indication of the distance of thesecond electronic device from the first electronic device is displayed(e.g., a textual indication of the distance and/or a graphicalindication of the distance, such as via the size of a displayedgeometric shape, as previously described). In some embodiments, inresponse to detecting a change in distance between the first electronicdevice and the second electronic device (1118 a) (e.g., the firstelectronic device has been moved, by the user, to a lesser or greaterdistance from the second electronic device, and/or the second electronicdevice has moved to a lesser or greater distance from the firstelectronic device), in accordance with a determination that the distancebetween the first electronic device and the second electronic device isgreater than the threshold distance (e.g., 10, 20, 40, 50, 100, 200, 300feet), a visual indication of the location of the second electronicdevice relative to the first electronic device is not displayed via thedisplay generation component (1118 e), such as user interfaces 1012 aand 1012 b in FIGS. 10E and 10F when Objects 1 and 2 are further thanthe threshold distance from device 500. For example, for both the firstand second locator processes, when the second electronic device is toofar away for the first electronic device to be able to establish asignal connection with the second electronic device, the firstelectronic device does not display an indication of the location (e.g.,distance and/or direction) of the second electronic device relative tothe first electronic device. In some embodiments, the first electronicdevice displays an indication that the second electronic device is toofar away to proceed with the first or second locator processes, and oncethe devices are within the threshold distance of one another, displaysthe visual indication of the location of the second electronic devicerelative to the first electronic device that includes the indication ofthe direction of the second electronic device relative to the firstelectronic device (e.g., if the first electronic device is performingthe first locator process).

The above-described manner of selectively displaying the visualindication of the location of the second electronic device relative tothe first electronic device ensures that inaccurate indications ofrelative location are not indicated in the user interface when accurateindications are unavailable or unlikely, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by avoiding erroneous movements for finding thesecond electronic device), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiently.

In some embodiments, the first locator process includes (1120 a), whiledisplaying, via the display generation component, a first respectiveuser interface for finding the second electronic device, wherein thefirst respective user interface is displayed in a first color, such asdisplaying user interface 1012 a in FIG. 10Q with a black background(e.g., having a background of the first color. In some embodiments, theindication(s) of the distance and/or relative location of the secondelectronic device with respect to the first electronic device is (are)displayed over the background), detecting a change in state of thesecond electronic device (1120 b), such as Object 1 being found in FIG.10S (e.g., the second electronic device is one or more earbuds, and thechange in state is that earbud, which was previously not in a user'sear, being placed in a user's ear. In some embodiments, the change instate is the earbud being placed in its case and/or charger. In someembodiments, the change in state is the earbud establishing a wired orwireless connection with another electronic device, such as asmartphone. In some embodiments, the first locator process includes(1120 a), in response to detecting the change in the state of the secondelectronic device, updating the first respective user interface to bedisplayed in a second color, different from the first color (1120 c),such as displaying user interface 1012 a in FIG. 10S with a greenbackground. For example, the background over which the indication(s) ofthe distance and/or relative location of the second electronic devicewith respect to the first electronic device is (are) displayed changescolor from the first color to the second color. In some embodiments,display of the indication(s) of the distance and/or relative location ofthe second electronic device with respect to the first electronic deviceis maintained. In some embodiments, the first electronic deviceadditionally or alternatively displays a separate (e.g., textual, iconicor graphic, etc.) visual indication that indicates that the state of thesecond electronic device has changed and/or the updated state of thesecond electronic device (e.g., “left earbud has been found or placed inear”).

The above-described manner of updating display of the finding userinterface provides a quick and efficient manner of indicating that thestate of the device being located has changed, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by avoiding unnecessary finding movements orinputs when the second electronic device may already be found, andfacilitating earlier termination of the locator process), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the second locator process includes (1122 a), whiledisplaying, via the display generation component, a second respectiveuser interface, different from the first respective user interface, forfinding the second electronic device, such as user interface 1012 b inFIG. 10R (e.g., a user interface specific to the second locator processand not the first locator process, such as including an indication ofthe distance between the first and second electronic devices, but notincluding an indication of the relative location of the secondelectronic device with respect to the first electronic device, aspreviously described), wherein the second respective user interface isdisplayed in the first color, such as displaying user interface 1012 inFIG. 10R with a black background (e.g., having a background of the firstcolor (e.g., the same corresponding color as in the first locatorprocess)), detecting the change in state of the second electronic device(1122 b), such as Object 2 being found in FIG. 10T (e.g., the secondelectronic device is one or more earbuds, and the change in state isthat earbud, which was previously not in a user's ear, being placed in auser's ear). In some embodiments, additional or alternative differencesbetween the first and second respective user interfaces are as describedabove. In some embodiments, the indication of the distance of the secondelectronic device from the first electronic device is displayed over thebackground. In some embodiments, the change in state is the earbud beingplaced in its case and/or charger. In some embodiments, the change instate is the earbud establishing a wired or wireless connection withanother electronic device, such as a smartphone. In some embodiments,the second locator process includes (1122 a), in response to detectingthe change in the state of the second electronic device, updating thesecond respective user interface to be displayed in the second color(1122 b), such as displaying user interface 1012 b in FIG. 10T with agreen background. For example, the background over which the indicationof the distance of the second electronic device from the firstelectronic device is displayed changes color from the first color to thesecond color (e.g., the same corresponding color as in the first locatorprocess). In some embodiments, display of the indication of the distanceof the second electronic device is maintained. In some embodiments, thefirst electronic device additionally or alternatively displays aseparate (e.g., textual, iconic or graphic, etc.) visual indication thatindicates that the state of the second electronic device has changedand/or the updated state of the second electronic device (e.g., “leftearbud has been found or placed in ear”).

The above-described manner of displaying the same/similar colorscorresponding to status changes of the second electronic device in thefirst and second locator processes provides a quick and efficient mannerof consistently indicating that the state of the device being locatedhas changed, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by avoidingunnecessary finding movements or inputs when the second electronicdevice may already be found, and facilitating earlier termination of thelocator process, whether the first electronic device is performing thefirst or the second locator process), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 11A-11F have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700, 900, 1300 and 1500) are also applicable in an analogousmanner to method 1100 described above with respect to FIGS. 11A-11F. Forexample, the locator processes described above with reference to method1100 optionally have one or more of the characteristics of locatorprocesses, separation alerts, object tracking, etc., described hereinwith reference to other methods described herein (e.g., methods 700,900, 1300 and 1500). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., a as described with respect to FIGS. 1A-1B, 3, 5A-5H)or application specific chips. Further, the operations described abovewith reference to FIGS. 11A-11F are, optionally, implemented bycomponents depicted in FIGS. 1A-1B. For example, displaying operation1102 a, receiving operation 1102 b, and initiating operations 1102 d and1102 e are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch screen 504, and event dispatcher module174 delivers the event information to application 136-1. A respectiveevent recognizer 180 of application 136-1 compares the event informationto respective event definitions 186, and determines whether a firstcontact at a first location on the touch screen corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Locating Associated Components

Users interact with electronic devices in many different manners. Insome embodiments, an electronic device is able to track the location ofan object or device. In some embodiments, the electronic device is ableto track the location of associated devices (e.g., a set of left andright earbuds) that can be separated from one another. The embodimentsdescribed below provide ways in which an electronic device facilitatesfinding associated components that are at one or more physicallocations, thus enhancing the user's interactions with the electronicdevice. Enhancing interactions with a device reduces the amount of timeneeded by a user to perform operations, and thus reduces the power usageof the device and increases battery life for battery-powered devices. Itis understood that people use devices. When a person uses a device, thatperson is optionally referred to as a user of the device.

FIGS. 12A-12TT illustrate exemplary ways in which an electronic devicefacilitates finding associated components that are at one or morephysical locations in accordance with some embodiments of thedisclosure. The embodiments in these figures are used to illustrate theprocesses described below, including the processes described withreference to FIGS. 13A-13J.

FIG. 12A illustrates an exemplary device 500 that includes touch screen504. In FIG. 12A, the electronic device 500 is displaying user interface1202. User interface 1202 includes a list 1206 of devices or objectswhose location can be tracked/viewed by device 500, such as list item1210 corresponding to John's Tablet, list item 1212 corresponding toJohn's Phone, and list item 1214 corresponding to John's Computer. Thelist 1206 also includes representations of components that areassociated with each other, such as list item 1208 corresponding toJohn's Earbuds (e.g., corresponding to a left earbud and a right earbudthat are associated with each other). In the example of FIG. 12A, listitems 1208-1214 include a name of the object that corresponds to thelist item (“John's Earbuds”, “John's Tablet”, etc.), a graphicalrepresentation of that object, labels which provide textual descriptionsabout the last time device 500 received information about a location ofthat object, and information about the last known location for thatobject.

Additionally, user interface 1202 also includes a representation of amap 1204. The representation of the map 1204 includes representations ofdevices or objects whose location can be tracked/viewed by device 500,and also includes representations of components that are associated witheach other, such as a representation of John's Earbuds 1216 displayed ata location on map 1204 corresponding to the last known location forJohn's Earbuds, a representation of John's Tablet 1218 displayed at alocation on map 1204 corresponding to the last known location for John'sTablet, a representation of John's Computer 1220 displayed at a locationon map 1204 corresponding to the last known location for John'sComputer, and a representation of John's Phone 1222 displayed at alocation on map 1204 corresponding to the last known location for John'sPhone. The representation of the map 1204 also includes a locationindicator 1224 that indicates a location of the electronic device 500.

In FIG. 12B, while displaying user interface 1202, the electronic device500 receives a selection of list item 1208 corresponding to John'sEarbuds (indicated by touch contact 1226). As will be discussed indetail later, in some embodiments, based on whether the components(e.g., the left earbud and the right earbud) associated with theselected list item are currently together or separated will result indifferent behaviors when that list item is selected. In the example ofFIG. 12B, John's Earbuds include a left earbud and a right earbud thatare at a same physical location (e.g., are not separated from oneanother). In some embodiments, the left earbud and right earbud areconsidered to be in the same location if the earbuds are within athreshold distance of each other (e.g., 3, 6, 12, 24, 36, 48, 96, 192,etc. inches apart) and/or if the earbuds are both located in the sameobject (e.g., a case).

In FIG. 12C, because the left earbud and right earbud of John's Earbudsare at a same physical location, in response to the input in FIG. 12B,user interface 1202 is updated to display a card user interface 1228corresponding to John's Earbuds. Specifically, card user interface 1228includes label 1234 indicating the object that is associated with card1228 (“John's Earbuds”), label 1236 which provides information about thelast known location of John's Earbuds and the last time the device 500received location information for John's Earbuds (“Near Mission Ave,Last Seen 6m ago”), and selectable options 1230 and 1232 correspondingto functions available for finding John's Earbuds (the left earbud andright earbud). Additionally, the representation of John's Earbuds 1216is centered in the representation of the map 1204, and device 500 ceasesto display representation of other, unselected items in map 1204.Because the left earbud and right earbud were determined to be in a samephysical location when the selection input 1226 was received in FIG.12B, the representation of John's Earbuds 1216 are displayed as a singlerepresentation in the representation of the map 1204 (as compared todisplaying separate representations for the left earbud and right earbudwhen the earbuds are not in the same physical location, as will bedescribed later with reference to FIGS. 12T and 12U).

In FIG. 12D, the electronic device 500 receives a selection ofselectable option 1232 (indicated by touch contact 1226). In FIG. 12E,in response to receiving the selection of selectable object 1232, theleft and right earbud of John's earbuds begin to emit an audio tone(indicated in card 1228 with text “A sound is playing. . .”), and card1228 is updated to display selectable option 1234 for toggling muting ofthe left earbud, selectable option 1238 for toggling muting of the rightearbud, and selectable option 1236 to toggle playback of the audio tone.In FIG. 12E, while the audio tone is playing at the left earbud andright earbud, the electronic device 500 receives a request to close card1228 (indicated by touch contact 1226).

In FIG. 12F, in response to receiving the request to close card 1228,the electronic device displays a user interface 1202 that is similar tothe user interface 1202 described with reference to FIG. 12A. In FIG.12G, while displaying user interface 1202, the electronic device 500receives a selection of list item 1208 corresponding to John's Earbuds,and updates user interface 1202 as shown in FIG. 12H. In the example ofFIG. 12H, the left and right earbuds of John's Earbuds are still at asame physical location when the input selecting list item 1208 wasreceived. Accordingly, user interface 1202 in FIG. 12H is similar to theuser interface 1202 described with reference FIG. 12C.

In FIG. 12i, the electronic device 500 receives a selection ofselectable option 1230. In FIG. 12J, in response to receiving theselection of selectable option 1230, device 500 initiates a finding modefor finding the left and right earbuds of John's Earbuds (e.g., findingthe left and right earbuds together, because they are in the samephysical location), and displays user interface 1240. In the example ofFIG. 12J, user interface 1240 is associated with a far (e.g., map-based)finding mode of device 500, because the distance between device 500 anda physical location of John's Earbuds is further than a thresholddistance (e.g., more than 25, 50, 100, 300, 500, 1,000, 5,000, 10,000,etc. feet). User interface 1240 includes a suggested route 1242 fornavigating from the location of device 500 (indicated by indicator 1224)to the location of John's Earbuds (indicated by representation 1216 ofJohn's Earbuds), and suggested route 1242 is displayed on a map 1204.User interface 1240 also includes card 1228 that includes informationabout the length of route 1242, travel time for the route, and if it isthe fasted suggested route. Card 1228 also includes selectable options1243-1246, which are selectable to switch suggested route 1242 betweendriving, walking, and transit routes, and includes selectable option1248 for starting navigation to John's Earbuds.

In FIG. 12K, the electronic device 500 receives a selection ofselectable option 1248 (indicated by touch contact 1226). In FIG. 12L,in response to selection of selectable option 1248, the electronicdevice 500 begins displaying driving directions to John's Earbuds. Userinterface 1240 displays the navigation route 1243 in the suggesteddirection of travel, and includes intermediate navigation directions1250 based on the current location of device 500 on the route 1243. Inthe example of FIG. 12L, intermediate navigation directions 1250 includeinformation informing the user to navigate to First Ave. (“Start onFirst Ave”), and because the user needs to navigate to “First Ave.”, thestreet First Ave. is displayed straight ahead (e.g., in the direction oftravel) in user interface 1240. In FIG. 12M, after some progression onthe route to John's Earbuds, the electronic device 500 has detected thatthe user has moved to a new position in route 1243. In response to thedevice's 500 new location along the route 1243, the user interface 1240updates the intermediate driving directions (“Proceed on Second Ave”)and updates the user interface in the direction of travel (e.g.,displays street “Second Ave.” straight ahead)). In FIG. 12N, after somemore progression on the route to John's Earbuds, the electronic device500 has again detected that the user has moved to a new position in theroute 1243. In response to the device's 500 new location along the route1243, the user interface 1240 updates the intermediate driving direction(“Earbuds on Right”), but does not update the user interface 1240 in thedirection of travel (e.g., continues to display the street “Second Ave.”straight ahead), because there are no more roads between John's Earbudsand the device 500.

In some embodiments, when a user moves within a threshold distance(e.g., 200, 100, 50, 25, 15, 10, 5 feet) of John's Earbuds, theelectronic device automatically transitions from the far finding mode(e.g., displaying driving directions) to a close finding mode (e.g.,displaying relative directions, similar to as described with referenceto method 1100) for the object being located. Various details of theclose finding mode are optionally as described with reference to method1100. For example, in FIG. 120, after device 500 has moved within thethreshold distance of John's Earbuds, device 500 transitions to theclose finding mode. In response to device 500 transitioning to the closefinding mode, user interface 1240 is updated to include directionindicator 1246 and distance indicator 1248. Direction indicator 1246graphically indicates the direction to John's Earbuds relative to theorientation of device 500 (e.g., similar to as described with referenceto method 1100). Distance indicator 1248 textually indicates thedistance between device 500 and John's Earbuds (e.g., similar to asdescribed with reference to method 1100). In some embodiments, as thelocation of device 500 and/or the object that is being located changes,direction indicator 1246 and distance indicator 1248 are updated in realtime. In the example of FIG. 120, direction indicator 1246 is indicatingJohn's Earbuds are to the right of device 500, and distance indicator1248 is indicating that John's Earbuds are 25ft to the right.

In FIG. 12P, device 500 has detected that John's Earbuds are directly infront of device 500 and are now 10 feet away from device 500. Inresponse to detecting that John's Earbuds are directly in front ofdevice 500, electronic device 500 updates direction indicator 1246 topoint straight ahead (indicating that John's Earbuds are straightahead), and updates distance indicator 1248 to the new distance betweendevice 500 and John's Earbuds (“10 feet ahead”).

In FIG. 12Q, device 500 has now detected that John's Earbuds aredirectly in front of device 500 and are 1 foot way from device 500. Inresponse, electronic device 500 continues to display the directionindicator 1246 pointing straight ahead (indicating that John's Earbudsare straight ahead) and updates distance indicator 1248 with the newdistance between device 500 and John's Earbuds (“1 foot ahead”).

In FIG. 12R, the electronic device 500 detects that John's earbuds havebeen found. In response to electronic device 500 detecting that theearbuds have been found, the electronic device 500 changes a color ofuser interface 1240 (represented by cross hatch fill in user interface1240) for indicating that the earbuds have been found, and also updatesuser interface 1240 to include status message 1250 for indicating thatthe earbuds have been found (“Found”). In some embodiments, theelectronic device determines that John's earbuds have been found whenthe earbuds change states (e.g., earbuds begins to be worn by a user,are placed in or attached to a (e.g., magnetic) case, and/or begincharging).

FIGS. 12S-12PP illustrate exemplary ways that the electronic devicefacilitates finding associated components that are at a differentphysical locations, thus requiring separate finding directions. In FIG.12S, electronic device 500 is displaying user interface 1202. Similar toas described with reference to FIG. 12A, user interface 1202 include alist 1206 of devices or objects whose location can be tracked/viewed bydevice 500, such as list item 1210 corresponding to John's Tablet, listitem 1212 corresponding to John's Phone, and list item 1214corresponding to John's Computer. The list 1206 also includesrepresentations of components that are associated with each other, suchas list item 1208 corresponding to John's Earbuds (e.g., correspondingto a left earbud and a right earbud that are associated with eachother).

User interface 1202 also includes a representation of a map 1204. Therepresentation of the map 1204 includes representation of the devices orthe objects whose location can be tracked/viewed by device 500, and alsoincludes representations of components that are associated with eachother, such as a representation of John's left earbud 1223 displayed ata location on map 1204 corresponding to the last known location forJohn's Earbuds, a representation of John's right earbud 1221 displayedat a location on map 1204 corresponding to the last known location forJohn's Earbuds, a representation of John's computer 1220 displayed at alocation on map 1204 corresponding to the last known location for John'sEarbuds, a representation of John's phone 1218 displayed at a locationon map 1204 corresponding to the last known location for John's Earbuds,and a representation of John's tablet 1222 displayed at a location onmap 1204 corresponding to the last known location for John's Earbuds. Inthe example of FIG. 12S, the earbuds associated with John's Earbuds aredisplayed with separate representations and at separate locations on map1204, because the earbuds are at different physical locations (incontrast to FIG. 12A when the earbuds associated with John's Earbuds aredisplayed with a single representation because the earbuds were at asame physical location). Additionally, list item 1208 includes adifferent textual description of the location of John's Earbuds (“Atdifferent locations”) as compared to list item 1208 in FIG. 12A (“NearYou”), because the left and right earbuds are now at different physicallocations (e.g., more than 3, 6, 12, 24, 36, 48, 96, 192 inches apart).

In FIG. 12T, while displaying user interface 1202, the electronic device500 receives a selection of list item 1208 corresponding to John'sEarbuds (e.g., via tap of contact 1226). As mentioned previously,depending on whether the locations of the left and the right earbud(e.g., the plurality of associated components corresponding to list item1208) are at the same location or are at separate locations, device 500will perform different actions when list item 1208 is selected. In theexample of FIG. 12T, John's Earbuds include a left earbud and a rightearbud that are at different physical locations. In some embodiments,the left earbud and right earbud are considered to be in differentlocations if the earbuds are more than a threshold distance apart (e.g.,5, 10, 20, 50, 100, 500, 1000, 2000, 5000 feet and/or if the earbuds arenot located in the same object (e.g., a case).

In FIG. 12U, in response receiving the selection of list item 1208 andbecause the left earbud and right earbud are at different physicallocations, list item 1208 is expanded to include the componentsassociated with John's Earbuds, including a child item 1252corresponding to John's Left Earbud, and a child item 1254 correspondingto John's right earbud—which is different than the behavior shown whenthe earbuds were together as described with reference to FIGS. 12G and12H). Child items 1252 and 1254 include information about theirrespective locations relative to device 500. As shown in FIG. 12U, childitem 1252 corresponding to John's Left Earbud includes label 1258 thatprovides information about the distance between the left earbud anddevice 500 (“2 miles”), and an estimated travel time to the earbud (“10minutes”). Similarly, child item 1254 corresponding to John's RightEarbud includes information about the distance between the right earbudand device 500 (“25 feet”), and an estimated travel time to the earbud(“2 minutes”). Additionally, because the left earbud and the rightearbud are separated (e.g., are separated by more than a thresholddistance), the representation of the map 1204 includes a representationof the left earbud 1221 and a representation of the right earbud 1223,and is centered at a location between John's Left Earbud and John'sRight Earbud, and also no longer displays representations of otherunselected items on map 1204.

In FIG. 12V, the electronic device detects a selection of child listitem 1252 corresponding to John's Left Earbud (indicated by touchcontact 1226). In FIG. 12W, in response to receiving the selection ofchild item 1252, the electronic device 500 updates the child list item1252 to include a selectable option 1260 for emitting audio at John'sLeft Earbud, a selectable option 1262 for initiating a process todisplay map-based directions to John's Left Earbud, and a selectableoption 1264 for initiating a close finding mode for finding John's LeftEarbud, as described above. Selectable option 1264 is disabled(represented by cross hatch fill), because the location of John's LeftEarbud is more than a threshold distance (e.g., 5, 10, 20, 50, 100, 500,1000, 2000, 5000 feet) from device 500.

In FIG. 12X, the electronic device receives a selection of child listitem 1254 corresponding to John's Right Earbud (indicated by touchcontact 1226). In FIG. 12Y, in response to receiving the selection ofchild list item 1254, the electronic device 500 updates child item 1254to include selectable option 1260 for emitting audio at John's RightEarbud, a selectable option 1262 for initiating a process to displaymap-based directions to John's Right Earbud, and selectable option 1264for initiating a close finding mode for finding John's Right Earbud, asdescribed above. Selectable option 1264 is enabled (as compared to beingdisabled in FIG. 12W), because the location of John's Right Earbud isless than a threshold distance (e.g., 5, 10, 20, 50, 100, 500, 1000,2000, 5000 feet) from device 500.

In FIG. 12Z, the electronic device 500 detects a selection (e.g., viatouch contact 1226) of selectable option 1264 corresponding to a requestto enter a close finding mode for John's Right Earbud. In FIG. 12AA, inresponse to receiving the selection in FIG. 12Z, device 500 displaysuser interface 1240 corresponding to the close finding mode previouslydescribed, including as described with reference to method 1100. Userinterface 1240 includes direction indicator 1246, which is indicatingJohn's Right Earbud is at a location to the right of device 500(direction indicator 1246 pointing to the right), and includes distanceindicator 1248, which is indicating that John's Right Earbud is 25 feetaway (“25 feet to the right”).

Additionally, because device 500 is currently in a finding mode for onecomponent of a plurality of associated components (e.g., John's RightEarbud, which is part of a set of associated components comprisingJohn's Right Earbud and John's Left Earbud), user interface 1240 alsoincludes toggle button 1250 corresponding to John's Left Earbud andtoggle button 1252 corresponding to John's Right Earbud. In someembodiments, user interface 1240 visually indicates which component(e.g., earbud) is currently being located by device 500. For example, inFIG. 12AA, because user interface 1240 includes finding information forJohn's Right Earbud, device 500 displays toggle button 1252 (the togglebutton corresponding to John's Right Earbud) with a particular visualcharacteristic (represented by solid fill in toggle button 1252).Similarly, because user interface 1240 does not currently includingfinding information for John's Left Earbud, the toggle button 1250corresponding to John's Left Earbud does not have the same visualcharacteristic as toggle button 1252.

In some embodiments, toggle buttons 1250 are selectable to cause findinginforming for a corresponding component/object to be displayed in theuser interface 1240. For example, in FIG. 12BB while device 500 isdisplaying finding information for John's Right Earbud, the electronicdevice 500 receives a selection of toggle button 1250 corresponding toJohn's Left Earbud (indicated by touch contact 1226). In FIG. 12CC, inresponse to receiving the selection of toggle button 1250, device 500enters into a far finding mode for John's Left Earbud, because the leftearbud is more than the threshold distance away from device 500, andceases displaying finding information for John's Right Earbud.Specifically, user interface 1240 includes map-based directions toJohn's Left Earbud, as previously described. User interface 1240includes a suggested route 1242 from the current location of device 500(indicated by indicator 1224) to the location of John's Left Earbud(indicated by the representation of John's Left Earbud 1223). The userinterface 1240 also includes card 1228 that includes information aboutthe length of route 1242, travel time for the route, and if it is thefasted suggested route. Card 1228 includes selectable options 1243-1246,which are selectable to switch between driving, walking, and transitroutes, and also includes selectable option 1248 for starting navigationto John's Left Earbud. Additionally, the user interface 1240 includestoggle buttons 1250 and 1252 for toggling between finding John's Leftand Right Earbuds, which were described above. In some embodiments,toggle buttons 1250 and 1252 are not included in user interface 1240when the device is in the far finding mode (e.g., displaying map-baseddirections).

In FIG. 12DD, the electronic device 500 receives a selection of togglebutton 1252 corresponding to John's Right Earbud (indicated by touchcontact 1226). In response to receiving the selection of toggle button1252, device 500 updates the user interface 1240 to include findinginformation for John's Right Earbud, and because John's Right earbud iswithin the threshold distance of device 500, device 500 againtransitions into the close finding mode, and user interface 1240includes relative directions to John's Right Earbud, as shown in FIG.12EE. Specifically, user interface 1240 includes direction indicator1246 and distance indicator 1248, as were previously described. In FIG.12FF, while displaying finding information for John's Right Earbud, theelectronic device 500 detects that John's Right Earbud is now directlyin front of device 500. In response to detecting the new location ofJohn's Right Earbud, the electronic device 500 updates directionindicator 1246 and distance indicator 1248 based on the new location ofJohn's Right Earbud. Specifically, device 500 updates directionindicator 1246 to point straight ahead (indicating that John's Earbudsare straight ahead), and updates the distance indicator 1248 with thenew distance between device 500 and John's Right Earbud (“15 feetahead”).

In FIG. 12GG, while displaying the updated direction and distanceinformation in the user interface 1240, the electronic devices detectsthat device 500 has again moved closer to John's Right Earbud, and thatthe right earbud is straight ahead. In response to detecting the newlocation of John's Right Earbud, the electronic device 500 continues todisplay direction indicator 1246 pointing straight ahead, and updatesdistance indicator 1248 with the new distance between device 500 andJohn's Right Earbud (“5 feet ahead”). In FIG. 12HH, the electronicdevice detects that the device 500 has again moved closer to John'sRight Earbud. In response to detecting the new location of John's RightEarbud, the electronic device 500 continues to display directionindicator 1246 pointing straight ahead and updates distance indicator1248 with the new distance between device 500 and John's Right Earbud(“1 foot ahead”).

In FIG. 12II, the electronic device 500 has detected that John's RightEarbud has been found. In some embodiments, earbuds (or other types ofcomponents) are determined to be found if the earbud was placed in orattached to a (e.g., magnetic) case, begins charging, becomes attachedto device 500 (e.g., in the case of a magnetic or otherwise attachableaccessory of device 500) and/or begins being worn by a user. In someembodiments, when the earbud is determined to be found, device 500updates user interface 1240 to provide a visual indication about the newstate of the earbud. For example, in FIG. 12II, in response to John'sRight Earbud having been found, device 500 changes a color of the userinterface 1240 (indicated by the cross hatch in user interface 1240),updates the user interface 1240 to include a status message 1250indicating that the earbud has been found, and updates a visualcharacteristic of the toggle button 1252 (represented by cross hatchfill) corresponding to the right earbud to indicate the earbud has beenfound. In some embodiments, toggle button 1252 is no longer selectable,or no longer displayed, after the right earbud has been found.

In some embodiments, when one of the earbuds (or components) in a pair(or more) of components are found, a process for finding a second earbud(or component) in the pair (or more) of components is automaticallyinitiated. For example, in FIG. 12JJ, in response to device 500detecting that John's Right Earbud has been located, the electronicdevice automatically (e.g., without user input for doing so) beginsdisplaying finding information for John's Left Earbud—the next earbud inJohn's Earbuds that is currently in a “not found” state. In someembodiments, an earbud (or component) is optionally determined to be ina “not found” state if the that earbud (or component) is not being wornby a user, is not being charged, is not placed in or attached to a (e.g.magnetic) case, is not attached to device 500, and/or is more than athreshold distance (e.g., 5, 10, 20, 50, 100, 500, 1000, 2000, 5000feet) from device 500. In FIG. 12JJ, user interface 1240 includesmap-based directions to John's Left Earbud, because the location of theearbud is more than the previously-described threshold distance forinitiating the far finding mode from device 500. Specifically, userinterface 1240 includes intermediate navigation directions 1250informing the user to navigate to First Ave. (“Start on First Ave”), andbecause the user needs to navigate to “First Ave.”, the street FirstAve. is displayed straight ahead (e.g., in the direction of travel) inuser interface 1240. In FIG. 12KK, the electronic device 500 hasdetected that the user has moved to a new position in the route 1243. Inresponse to the device's 500 new location along the route 1243, the userinterface 1240 updates the intermediate driving directions (“Proceed onSecond Ave”), and is reoriented in the direction of travel (e.g.,displays street “Second Ave.” straight ahead)). In FIG. 12LL, theelectronic device 500 has again detected that the user has moved to anew position in the route 1243. In response to the device's 500 newlocation along the route 1243, the user interface 1240 updates theintermediate driving direction (“Left Earbud on Right”), but does notreorient the user interface 1240 in the direction of travel (e.g.,continues to display the street “Second Ave.” straight ahead) becausethere are no more roads between John's Left Earbud and the user.

As previously mentioned, when device 500 moves within the thresholddistance of a component that is currently being located, the electronicdevice switches from far finding mode (e.g., displaying drivingdirections) to close finding mode (e.g., displaying relative directions)for the object being located. For example, in FIG. 12MM, after device500 has moved within the threshold distance of John's Left Earbud,device 500 changes from displaying map-based directions to displayingrelative directions. In response to device 500 switching to closefinding mode, user interface 1240 is updated to include directionindicator 1246 and distance indicator 1248, which indicate that John'sleft earbud is at a location to the right of device 500, and that theleft earbud is 25 feet away.

In FIG. 12NN, device 500 has detected that John's Left Earbud are nowdirectly in front of device 500 and that John's Left Earbud is now 10feet from device 500. In response, electronic device 500 updatesdirection indicator 1246 to point straight ahead (indicating that John'sLeft Earbud is now straight ahead) and updates distance indicator 1248to indicate the new distance between device 500 and John's Left Earbud(“10 feet ahead”). In FIG. 1200, device 500 has now detected that John'sLeft Earbud is now directly in front of device 500 and is now 1 footfrom device 500. In response, electronic device 500 continues to displaythe direction indicator 1246 pointing straight ahead (indicating thatJohn's Left Earbud is straight ahead) and updates distance indicator1248 to indicate the new distance between device 500 and John's LeftEarbud (“1 foot ahead”).

In FIG. 12PP, the electronic device 500 has detected that John's LeftEarbud has been found. As discussed previously, in some embodiments,earbuds (or other types of components) are determined to be found if theearbud was placed in or attached to a (e.g., magnetic) case, beginscharging, becomes attached to device 500 (e.g., in the case of amagnetic or otherwise attachable accessory of device 500), and/or beginsbeing worn by a user. In some embodiments, when the earbud is determinedto be found, device 500 updates user interface 1240 to provide a visualindication about the new state of the earbud. For example, in FIG. 12PP,in response to John's Left Earbud having been found, device 500 changesa color of the user interface 1240 (indicated by the cross hatch in userinterface 1240), updates the user interface 1240 to include a statusmessage 1250 indicating that the earbud has been found (“Found”), andupdates a visual characteristic of the toggle button 1250 (representedby cross hatch fill in the toggle button 1250) corresponding to the leftearbud to indicate the earbud has been found. In some embodiments,toggle button 1250 is no longer selectable, or no longer displayed,after the left earbud has been found. As shown in FIG. 12PP, both togglebuttons 1250 and 1252 are displayed as inactive, because both John'sLeft and Right Earbuds have been found.

In some embodiments, the electronic device 500 displays disambiguationoptions when input is received that corresponds to more than onecomponent in a set of associated components, such as in FIGS. 12QQ-12TT.In FIG. 12QQ, device 500 is displaying a user interface 1202 that issimilar to the user interface described previously with reference toFIG. 12U. While displaying user interface 1202, the electronic device500 detects a selection of menu item 1208 corresponding to John'sEarbuds (indicated by contact 1226). In the example of FIG. 12QQ, John'sLeft and Right Earbuds are separated from each other, such as in FIG.12U.

In FIG. 12RR, in response to receiving the selection of menu item 1208,the electronic device 500 updates user interface 1204 to display a carduser interface 1228 corresponding to John's Earbuds (e.g., while John'sLeft and Right Earbuds are separated from each other). Specifically,card user interface 1228 includes label 1234 indicating the object(s)that is associated with card 1228 (“John's Earbuds”), label 1236 thatprovides information about the last known location of the object and thelast time the device 500 received location for John's Earbuds (“Atdifferent locations, Last Seen 5m ago”), and selectable options 1230 and1232 corresponding to functions available for finding John's Earbuds. Inthe example of FIG. 12RR, label 1236 includes different textualinformation than label 1236 in FIG. 12H (“Near You”) because the leftand right earbuds are at different physical locations. Additionally, therepresentation of the map 1204 includes a representation of the leftearbud 1221 and a representation of the right earbud 1223 at differentlocations on map 1204, and map 1204 is centered at a location betweenJohn's Left Earbud and John's Right Earbud.

In FIG. 12SS, while displaying user interface 1202, the electronicdevice receives an input selecting selectable option 1230 (indicated bycontact 1226). In FIG. 12TT, in response to the input in FIG. 12SS, theelectronic device 500 displays a disambiguation menu 1290 overlaid onuser interface 1202, because the left and right earbud in John's Earbudsare at separate locations. In contrast, if the earbuds had been together(e.g., at a same location) when the selectable option 1230 was selected,the device would operate in a manner similar to what was described withreference to FIGS. 12I-12R. Selection input directed to items of thedisambiguation menu (e.g., selection of Left or Right) optionally causesfinding information for that component to be displayed by electronicdevice 500 in the manners described previously.

FIGS. 13A-13J are flow diagrams illustrating a method 1300 of findingassociated components that are at one or more physical locations inaccordance with some embodiments, such as in FIGS. 12A-12TT. The method1300 is optionally performed at an electronic device such as device 100,device 300, or device 500 as described above with reference to FIGS.1A-1B, 2-3, 4A-4B and 5A-5H. Some operations in method 1300 are,optionally combined and/or order of some operations is, optionally,changed.

As described below, the method 1300 provides ways to find associatedcomponents that are at one or more physical locations. The methodreduces the cognitive burden on a user when interacting with a userinterface of the device of the disclosure, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, increasing the efficiency of the user's interaction with theuser interface conserves power and increases the time between batterycharges.

In some embodiments, method 1300 is performed at an electronic device incommunication with a display generation component and one or more inputdevices (e.g., a mobile device (e.g., a tablet, a smartphone, a mediaplayer, or a wearable device) including wireless communicationcircuitry, optionally in communication with one or more of a mouse(e.g., external), trackpad (optionally integrated or external), touchpad(optionally integrated or external), remote control device (e.g.,external), another mobile device (e.g., separate from the electronicdevice), a handheld device (e.g., external), and/or a controller (e.g.,external), etc.)). In some embodiments, the display generation componentis a display integrated with the electronic device (optionally a touchscreen display), external display such as a monitor, projector,television, or a hardware component (optionally integrated or external)for projecting a user interface or causing a user interface to bevisible to one or more users, etc.

In some embodiments, the electronic device receives (1302 a), via theone or more input devices, a first input (e.g., an input such as a touchinput, mouse input, keyboard input, etc.) corresponding to a request tolocate a first component of a first set of two or more components thatare, for example, paired together, such as, in FIG. 12Z, touch contact1226 selecting selectable option 1264 for locating John's Right Earbud.For example, the electronic device receives a touch input correspondingto a request to find a mouse (e.g., first component) of a set ofcomponents comprising a mouse and a computer. In some embodiments, thefirst component (e.g., the mouse) is wirelessly (or via wiredconnection) paired with other components (e.g., the computer) in the setof two or more components via a Bluetooth connection or other similarconnection such that the components operate in conjunction with oneanother when they are in use together. In some embodiments, theelectronic device has information (e.g., from prior configuration of theelectronic device for use with the set of components) that thecomponents are paired together. In some embodiments, the first component(e.g., the mouse) and other components (e.g., the computer) in the setof two or more components are located at different locations in aphysical environment (e.g., a room, or a city, or a state). In someembodiments, the location of the first component (e.g., the mouse) isunknown to the user, and because the location of the first component isunknown to the user, the electronic device receives a request, from auser, to locate the first component (e.g., to initiate a finding mode tofind the first component, such as described with reference to method1100).

In some embodiments, representations of components in the set of two ormore components are displayed in a user interface (e.g., overlaid on amap user interface at locations corresponding to each componentslocation). In some embodiments, selecting a respective representationdisplayed in the user interface optionally causes the display of one ormore second selectable options associated with one or more actions for acomponent corresponding to the selected representation. For example,after selecting a particular representation displayed in the userinterface, a selectable option for displaying information for locatingthe component corresponding to the selected representation is optionallydisplayed. In some embodiments, the electronic device optionally detectsa touch input directed to the selectable option associated withdisplaying information for locating the component corresponding to theselected representation. In some embodiments, some of the components inthe set of two or more components provide similar functionality, whileother components in the set of two or more components provide adifferent functionality. For example, a set of components optionallycomprises a left earphone/earbud, a right earphone/earbud, and/or acharging component capable of charging the left earphone and rightearphone (e.g., a charging case into which the left and right earphonesare placed for storage and/or charging). The left earphone and rightearphone optionally provide a similar function (e.g., playback music) ina synchronized manner (e.g., playback of left and right channels ofaudio, respectively) due to being paired together, while the chargingcomponent does not provide the similar function (e.g., does not playbackmusic). In some embodiments, a single earbud can be used to play monoaudio, both earbuds can be used together to play synchronized audio suchas stereo audio or spatial audio. In some embodiments, either earbud canbe used as a microphone for recording audio for use during a video orphone call. In some embodiments, both earbuds can be used together tocancel ambient sounds around the user (e.g., using active noisecancellation techniques).

In some embodiments, in response to receiving the first input, theelectronic device updates (1302 b) a user interface displayed, via thedisplay generation component, to include information indicating alocation of first component, such as the user interface 1240 includingdirection and distance indicators 1246 and 1248 for John's Right Earbudin FIG. 12AA. For example, a user interface currently displayed by theelectronic device is updated to include information for locating thefirst component, such as described with reference to method 1100. Insome embodiments, the information optionally includes directions fornavigating to a location of the first component. For example, thedirections optionally include directions for navigating from a locationwhere the first input was received on the electronic device (e.g.,starting location) to a current location of the first component (e.g.,ending location). In some embodiments, when the first component is athreshold distance away from a location of the electronic device, thenavigation directions are directions at a first granularity level (e.g.,driving directions when the first component is more than 2, 3, 7, 10, 15miles away from the location of the first component). In someembodiments, when the first component is less than a threshold distanceaway from a location of the electronic device, the navigation directionsare directions at a second granularity level (e.g., walking directionswhen the first component is less than 2, 3, 7, 10, 15 miles away fromthe location of the first component). In some embodiments, thegranularity of the directions displayed in the user interface changes asa user of the electronic device moves closer or further away from thelocation of the first component. In some embodiments, the informationfor locating the first component is distance and/or relative directioninformation, such as “to the left, to the right, straight ahead, behind”(e.g., when the component is determined to be relatively close to thedevice, such as within 10, 50, 100, 500, 1000 feet), rather than drivingdirections (e.g., which are displayed when the component is determinedto be relatively far from the device, such as more than 10, 50, 100,500, 1000 feet).

In some embodiments, while displaying the updated user interface, theelectronic device receives (1302 c) an indication that the firstcomponent has been located, such as the indication received to causedevice 500 to display user interface 1240 for John's Right Earbud inFIG. 1211. For example, detecting that a user has found the firstcomponent (e.g., user has located the first component). In someembodiments, the electronic device receives an indication (e.g.,detects) that the first component has been located when a state withrespect to the first component changes. For example, if the firstcomponent was in a non-charging state when the first input (e.g., forrequesting information on locating the first component) was received,and the first component has changed to a charging state at some timeafter the first input was received by the electronic device (e.g.,because the earbud has been placed in its charging case), the electronicdevice optionally receives an indication (e.g., from the charger and/orthe first component) that the first component has been located.Additionally, or alternatively, the electronic device optionallyreceives the indication that the first component has been located inresponse to a determination that the first component is in contact witha user (e.g., the first component is touching the user and/or the firstcomponent is being worn by the user, such as the earbud being placed inthe user's ear). Additionally, or alternatively, the electronic deviceoptionally receives the indication that the first component has beenlocated when the first component becomes in contact (e.g., insert in,placed on top of, or in contact with) a second component of the set oftwo or more components. In some embodiments, the electronica deviceoptionally receives the indication (e.g., from the electronic device)that the first component has been located in response to a userselecting a “found” selectable option displayed in the user interfacewhile displaying information for locating the first component.

In some embodiments, in response to receiving the indication that thefirst component has been located (1302 d) (e.g., detecting that a userhas located the first component), the electronic device displays (1302e) a user interface for locating a second component of the first set oftwo or more components, different from the first component, such asupdating the user interface to include finding information for John'sLeft Earbud in FIG. 12JJ. For example, automatically (e.g., without userinput for doing so, other than the device determining that the firstcomponent has been located) updating the user interface to includefinding information for a second component after the first component hasbeen located, such as described with reference to method 1100. In someembodiments, when the electronic device receives an indication that thefirst component has been located, the electronic device ceases displayof the information for locating the first component in the userinterface. In some embodiments, if the electronic device receives anindication that the second component is already located (e.g., notmissing), the electronic device does not display information forlocating the second component. Thus, in some embodiments, the electronicdevice automatically sequentially initiates finding processes forcomponents that are paired together as those components are indicated asbeing located. In some embodiments, the information associated withlocating the second component optionally includes directions fornavigating to a location of the second component. For example, thedirections optionally include directions for navigating from a locationof the electronic device where the first input was received (e.g., astarting location) to a current location of the second component (e.g.,an ending location).

In some embodiments, when the second component is a threshold distanceaway from a location of the electronic device, the navigation directionsare directions at a first granularity level (e.g., driving directions ifthe second component is more than 2, 3, 7, 10, 15 miles away from thelocation of the first component). In some embodiments, when the secondcomponent is less than a threshold distance away from a location of theelectronic device, the navigation directions are directions at a secondgranularity level (e.g., walking directions if the second component isless than 2, 3, 7, 10, 15 miles away from the location of the secondcomponent). In some embodiments, the granularity of the directionsdisplayed in the user interface changes as a user of the electronicdevice moves closer or further away from the location of the secondcomponent. In some embodiments, the information for locating the secondcomponent is distance and/or relative direction information, such as “tothe left, to the right, straight ahead, behind” (e.g., when thecomponent is determined to be relatively close to the device, such aswithin 10, 50, 100, 500, 1000 feet), rather than driving directions(e.g., which are displayed when the component is determined to berelatively far from the device, such as more than 10, 50, 100, 500, 1000feet). In some embodiments, if a third component is paired with thefirst and second components, upon determining that the second componenthas been located, the electronic device automatically updates the userinterface to include finding information for the third component. Insome embodiments, if the device is displaying finding information for acomponent that is not paired with (e.g., associated with) othercomponents and/or if the component is paired with other components thatare already designated as having been located, in response determiningthat the component has been located, the electronic device does notautomatically display finding information for another component (e.g.,and instead terminates the finding process).

The above-described manner of updating a user interface to includeinformation associated with locating a first component, and updating theuser interface to include information associated with locating a secondcomponent when the first component has been located, provides anefficient way for locating components that are associated with eachother in a set of two or more components and also reduces inputs ascompared to requiring a user to separately locate differentdevices/components, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first set of two or more components includes afirst earbud and a second earbud that are a pair of earbuds for playbackof audio from a respective electronic device (1304 a), such as John'sLeft Earbud and John's Right Earbud as described with reference to FIG.12U (e.g., when the first earbud and the second earbud are within athreshold distance from the respective electronic device). For example,the first set of components includes audio playback devices such as aleft earbud (e.g., first earbud) and a right earbud (e.g., a secondearbud). In some embodiments, the first earbud and second earbudcommunicate (e.g., with the respective electronic device) independentlyof each other (e.g., perform one or more functions independent of othercomponents, such as being able to play audio of a given channel of audioindependently of whether the other component is currently playingaudio). In some embodiments, components in the first set transmit (e.g.,directly or indirectly) information regarding their status to theelectronic device. For example, the left earbud (e.g., the first earbud)optionally independently communicates a physical location and/or astatus of charge of the left earbud directly or indirectly to theelectronic device. Similarly, the right earbud (e.g., the second earbud)optionally independently communicates a physical location and/or statusof charge of the right earbud directly or indirectly to the electronicdevice. In some embodiments, the first component corresponds to thefirst earbud and the second component corresponds to the second earbud.In some embodiments, the two earbuds operate together when both areplaced in a user's ears to play synchronized multi-channel audio.

The above-described manner of the inclusion of earbuds in the first setof two or more components provides an efficient way for locatingcomponents in the first set, including earbuds that are wirelesslypaired together, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first set of two or more components include asecond electronic device (e.g., a computer, tablet, phone, an earbud, orother type of electronic device), different from the electronic device,and a charger for charging the second electronic device (1306 a), suchas if the described John's Computer in FIGS. 12A-12TT corresponded toboth a computer and a charger for that computer. For example, the earbudis placed in a charging case for charging the earbud). In someembodiments, the charger is wirelessly paired with the second electronicdevice to provide an indication of a charge status of the secondelectronic device. For example, the components of the set of two or morecomponents at least include an electronic device and a charger. In someembodiments, the electronic device corresponds to a computer, tablet,phone, earbud, or other type of electronic device, and the charger ofthe electronic device is wireless paired with the second electronicdevice to provide an indication about a status of the second electronicdevice (e.g., to the electronic device). In some embodiments, theindication optionally indicates a continuous charge level of the secondelectronic device or optionally indicates a charge level when a batteryof the second electronic device is below a threshold charge level (e.g.,1%, 2%, 3%, 5%, 10%, 20%). In some embodiments, the charger of thesecond electronic device also functions as a case for the secondelectronic device. In some such embodiments, the case optionallyattaches to, supports, or otherwise connects the charger to the secondelectronic device. In some embodiments, when the charger also functionsas a case, the charger/case is able to detect if a component (e.g., thesecond electronic device) currently in contact with and/or inserted intothe case has been previously associated (e.g., paired) together with thecharger. In some embodiments, the second electronic corresponds to thefirst component and the charger for the second electronic devicecorresponds to the second component.

The above-described manner of the inclusion of an electronic device anda charger for the electronic device in the first set of two or morecomponents provides an efficient way for locating components in thefirst set including an electronic device and a charger of the electronicdevice, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient, which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the updated user interface includes one or moreselectable options for switching between finding the first component ofthe first set of components and the second component of the first set ofcomponents (1308 a), such as the toggle buttons 1250 and 1252 in FIG.12AA (e.g., selectable buttons that correspond to respective componentsin the set of two or more components and are selectable to cause findinginformation to be displayed in the updated user interface for thecomponent corresponding to the selected button, for example to togglebetween finding a left earbud and a right earbud). In some embodiments,while displaying the updated user interface and before receiving theindication that the first component has been located, the electronicdevice receives (1308 b), via the one or more input devices, a secondinput directed to the one or more selectable options that corresponds toa request to switch to finding the second component of the first set ofcomponents, such as touch contact 1226 selecting toggle button 1250 inFIG. 12BB (e.g., while the updated user interface is displayinginformation for locating the first component and while the firstcomponent has not yet been located, the electronic device receives arequest from a user corresponding to a request to start finding thesecond component).

In some embodiments, in response to receiving the second input (1308 c),the electronic device ceases (1308 d) display of the informationindicating the location of the first component in the updated userinterface, such as the information for the right earbud no longer beingdisplayed in FIG. 12CC. In some embodiments, in response to receivingthe second input (1308 c), the electronic device displays (1308 e), inthe updated user interface, information indicating a location of thesecond component, such as, in FIG. 12CC, the user interface 1240includes finding information for John's left earbud. For example, if arequest to start locating a second component is received whileinformation for finding the first component is being displayed in theupdated user interface (e.g., an indication of a location of the firstcomponent in the updated user interface) and before receiving anindication that the first component has been located, the updated userinterface ceases displaying information for locating the first componentand begins to display information for locating the second component(e.g., information indicating a location of the second component). Insome embodiments, the information displayed in the updated userinterface for locating the second component is based on the location ofthe second component in a physical environment. For example, if thelocation of the second component is more than a threshold distance froma location of the electronic device (e.g., that received the input toswitch to finding the second component), the information indicating alocation of the second component optionally includes displaying thesecond component at a location in a map corresponding to the location ofthe second component in a physical environment. Similarly, if thelocation of the second component is less than a threshold distance froma location of the electronic device (e.g., that received the input toswitch to finding the second component), the information indicating alocation of the second component optionally includes an indication of adistance to the second component from the electronic device and/orrelative directions to second component such as “to the left, to theright, straight ahead, behind” (e.g., when the component is determinedto be relatively close to the device, such as within 10, 50, 100, 500,1000 feet), rather than driving directions or a map (e.g., which aredisplayed when the component is determined to be relatively far from thedevice, such as more than 10, 50, 100, 500, 1000 feet).

The above-described manner of displaying finding information for asecond component when a request to switch from finding the firstcomponent to finding the second component is received provides anefficient way of switching between finding information for differentcomponents, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient, which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiently.

In some embodiments, while displaying the updated user interfaceincluding the information indicating the location of the firstcomponent, wherein the updated user interface is displayed in a firstcolor (e.g., such as the color of user interface 1240 in FIG. 12HH)(e.g., while the first component has not been located, the updated userinterface is displayed in a first color, which indicates that the firstcomponent is currently being located. For example, the first color isblack, blue, red, etc.). In some embodiments, the first color is thebackground color over which the information indicating the location ofthe first component is displayed), the electronic device receives (1310a) an indication that a state of the first component has changed (e.g.,the first component is no longer being located (e.g., moved from a“being located” state to a new state (e.g., found state), or the firstcomponent is placed in a charger, or the first component is placed in auser's ear (if the first component is an earbud))). In some embodiments,in response to receiving the indication that the state of the firstcomponent has changed, the electronic device displays (1310 b) theupdated user interface in a second color, different from the firstcolor, such as the user interface 1240 changing a background color fromFIG. 12HH to FIG. 12II (represented by a cross hatch fill in userinterface 1240).

For example, when the first component that is currently being locatedhas changed from a “being located” state, the updated user interfacechanges colors (e.g., to green) to provide an indication of the newstate of the first component. In some embodiments, the background of theupdated user interface changes to the second color while stilldisplaying the information indicating the location of the firstcomponent. In some embodiments, when the first component changes to thenew state (e.g., a “located” state), the updated user interface includesan indication (e.g., notification) associated with how the firstcomponent changed to the new state (e.g., displays graphical informationsuch a representation of the first component being placed in a user'sear, being placed in a (e.g., charging) case, etc. and/or textualinformation such as “first component has been placed in a user's ear”,“first component has started charging”, “first component has been placedin a case”, etc.). In some embodiments, the state that the firstcomponent changes to (e.g., “placed in a user's ear”, “now charging”,“placed in a case”, etc.) determines the color of the updated userinterface (e.g., the color of the background of the updated userinterface), with different colors corresponding to different updatedstatus of the first component. In some embodiments, the backgroundchanges to correspond to a “being located” (e.g., not found) state if auser provides an input indicating that the component has not been foundor when the updated user interface begins displaying information forlocating a second component that is not currently located (e.g., in a“not found/located” state). In some embodiments, in response to thestate change (or, alternatively, for particular state changes), theelectronic device switches to the user interface for finding the secondcomponent. In some embodiments, when the second component is located thecolor of the user interfaces changes in a manner similar to/the same asthe manner described when the first component changes states.

The above-described manner of changing a display color of the updateduser interface from a first color to a second color when the componenthas changed states provides an efficient way of indicating a new stateof the first component, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient,which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the state of the first component includes acharging state of the first component (1312 a), such as displaying theuser interface 1240 in FIG. 1211 when John's right earbud startedcharging. For example, the electronic device receives the indication ofa change in state when the first component enters a charging state. Insome embodiments, when the first components changes to a charging statefrom a “not found” state (e.g., being located state). In someembodiments, the first component enters a charging state when the firstcomponent begins charging from a charger that has been previouslyassociated (e.g., paired) with the first component. In some embodiments,if the first component begins to be charged with a charger that has notbeen previously associated (e.g., paired) with the first component, thefirst component does not enter (e.g., change to) a charge state. In someembodiments, if the first component begins charging (e.g., changes to acharging state), a display color of the updated user interface changesfrom a first display color to a second display color, where the secondcolor corresponds to the charging state. In some embodiments, the firstcomponent and/or the charger that is charging the first componentdirectly and/or indirectly communicates with the electronic device toallow the electronic to receive an indication that the first componenthas changed to a charging state. In some embodiments, when the firstcomponent enters the charging state, the first component is indicated asfound/located. In some embodiments, the second component functions in amanner similar to/the same as the first component.

The above-described manner of changing a display color of the updateduser interface from a first color to a second color when the componenthas moved to a charging state provides an efficient way of indicating anew state of the first component, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the state of the first component includes whetherthe first component is in a case associated with the first component(1314 a), such as displaying the user interface 1240 in FIG. 1211 ifJohn's Right earbud is placed into a case. For example, the electronicreceives the indication that the first component has changed states whenthe first component is placed in (or moves within a threshold distance)of a case associated with the first component. In some embodiments, thedetermination that the first component is in a case associated with thefirst component is additionally or alternatively based on magnetic,electric, NFC and/or mechanical coupling between the first component andthe case. In some embodiments, when it is detected that the firstcomponents is placed in a case associated with the first component, thefirst component is identified as having been found. In some embodiments,the first component and/or the case that the first component is placedin communicates directly and/or indirectly with the electronic device toindicate that the first component has been placed in the case. In someembodiments, if the first component is placed in a case that is notpaired with the first component (e.g., was not previously pairedtogether), the electronic device does not receive an indication that thefirst component has been placed in a case (e.g., the first componentremains in the same state (e.g., “lost/missing” state)). In someembodiments, if the first component is placed into an associated case(e.g., a case that is paired with the first component), the color of theupdated user interface changes from a first color to a second colorcorresponding to “case insertion state”. In some embodiments, thebackground changes to correspond to a “not located” state if a userprovides an input indicating that the component has not been found orthe updated user interface begins displaying information for locating asecond component that is in a not located state. In some embodiments,the second component functions in a manner similar to/the same as thefirst component. In some embodiments, the case associated with the firstcomponent is configured to charge the first component (e.g., causes thefirst component to enter a charging state if the first component isinserted into the case).

The above-described manner of changing a display color of the updateduser interface from a first color to a second color when the componenthas been placed into an associated case provides an efficient way ofindicating that the first component has been found and is now in a case,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient, which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the state of the first component includes whetherthe first component is being worn by a user (1316 a), such as displayingthe user interface 1240 in FIG. 12II if John's Right Earbud starts beingworn by a user (e.g., of the electronic device). For example, theelectronic device receives the indication the first component haschanged states when the first component begins to be worn by a user(e.g., in contact with the body of a user (e.g., in ear, in hand, onwrist, on head, etc.)). In some embodiments, the first component detectsthat it is being worn by a user based on sensor measurements from thefirst component device, such as a proximity sensor that indicatesproximity of the component to a portion of a user's body, or a biometricsensor such as a pulse or face or eye sensor that detects the presenceof a biometric feature of the user. In some embodiments, when the firstcomponent begins to be worn by a user, the first component communicatesdirectly and/or indirectly with the electronic device to indicate thatthe first component is being worn by a user. In some embodiments, whenthe electronic device receives the indication that the first componentis being worn by a user, the color of the updated user interface changesfrom a first color to a second color to correspond to a state in whichthe user is wearing the first component. In some embodiments, thebackground changes to correspond to a “not located” state if a userprovides an input indicating that the component has not been found orthe updated user interface begins displaying information for locating asecond component that is in a “not located” state. In some embodiments,one or more proximity sensors of the first component determines if thefirst component is being worn by a user (e.g., if an object is within athreshold distance of the one or more proximity sensors of the firstcomponent). In some embodiments the second component in a manner similarto/the same as the first component.

The above-described manner of changing a display color of the updateduser interface from a first color to a second color when the componentis being worn by a user provides an efficient way of indicating that thefirst component has been found and is being worn by a user, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient, which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiently.

In some embodiments, while displaying the updated user interface thatincludes the information indicating the location of the first component,the electronic device displays (1318 a), in the updated user interface,a visual indication indicating that the first component of the first setof two or more components is currently being located, such as togglebutton 1252 having a different visual characteristic than toggle button1250 in FIG. 12HH (e.g., while the updated user interface is includinginformation for located the first component, a visual indication isdisplayed that indicates the first component is currently beinglocated). In some embodiments, while displaying the user interface forlocating the second component of the first set of two or morecomponents, the electronic device displays (1318 b), in the updated userinterface, a visual indication indicating that the second component ofthe first set of two or more components is currently being located suchas toggle button 1252 having a different visual characteristic thantoggle button 1250 in FIG. 12CC (e.g., while the updated user interfaceis including information for located the second component, a visualindication is displayed, in the updated user interface, that indicatesthat the second component is currently being located). In someembodiments, the updated user interface optionally includes selectableoptions corresponding to the components in the set of two or morecomponents, which are selectable to display information for locating arespective component (e.g., the respective component corresponding tothe selected selectable option). In some such embodiments, when theupdated user interface includes information for locating the firstcomponent (e.g., is indicating a location of the first component), theselectable option corresponding to the first component is optionallyshown with a first visual characteristic and the selectable options thatdo not correspond to the first selectable option are shown in adifferent visual characteristic.

The above-described manner of visually indicating which component of theset of two or more components is currently being located in the updateduser interface provides an efficient way of indicating which componentis currently being located, which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient,which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first input is received while the electronicdevice is displaying a second user interface, different from the userinterface, that includes a representation of a map and one or moreselectable items corresponding to one or more objects (e.g., when theinput corresponding to the request to locate a first component isreceived, the electronic device is displaying a user interface thatincludes a representation of a map and one or more selectable items thatcorrespond to objects that can be located or found using the findingprocesses described herein). In some embodiments, the one or moreselectable items are items in a list. In some such embodiments, when arespective selectable item is selected in the list, a graphical (ortextual representation) of the component corresponding to the selecteditem is displayed at a location on the representation of the mapcorresponding to a physical location of the component.

In some embodiments, while displaying the second user interface andbefore receiving the first input, the electronic device receives (1320a), via the one or more input devices, a second input selecting arespective selectable item of the one or more selectable items, such astouch contact 1226 selecting list item 1208 in FIG. 12T (e.g., beforethe input corresponding to the request to display information forlocating the first component is received, receiving a selection of oneof the selectable items). In some embodiments, in response to receivingthe second input (1320 c), in accordance with a determination that therespective selectable item corresponds to a respective set of two ormore associated components (e.g., if the selected item corresponds to aset of two or more associated components, such as associated left andright earbuds), the electronic device concurrently displays (1320 d), onthe representation of the map in the second user interface, a pluralityof representations of objects corresponding to components in therespective set of two or more associated components at locations on therepresentation of the map corresponding to physical locations of the twoor more associated components, such as the representation of John'sRight Earbud 1221 and the representation of John's Left Earbud 1223 inFIG. 12U.

For example, if the selected item of the plurality of selectable itemsdisplayed in the second user corresponds to a respective set of two ormore associated components, then the second user interface displays, onthe representation of the map, a plurality of representations of objectscorresponding to the components in the respective of two or moreassociated components. For example, if a selectable item is selectedthat corresponds to a respective set that includes (e.g., a pair of)earbuds, representations of objects, including the earbuds, in therespective set are displayed concurrently with the representation of themap—including displaying a representation of a first item in the pair ofearbuds and a representation of a second item in the pair of earbuds inthe representation of the map. In some such examples, therepresentations of objects corresponding the earbuds are displayed atlocations on the map corresponding to the locations of the earbuds in aphysical environment. In some embodiments, the representations ofobjects displayed on the map are selectable to initiate a request forlocating a particular component. In some embodiments, the locations ofthe earbuds (e.g., components) are at a same location in a physicalenvironment (e.g., within a threshold distance from the same physicallocation). In some such embodiments, the representations of objects aredisplayed at a location on the representation of the map correspondingto same location of the earbuds in the physical environment. In someembodiments, the locations of the earbuds (e.g., components) are atdifferent locations in a physical environment. In some such embodiments,the representations of objects are displayed at different locations onthe representation of the map corresponding to the different locationsof the earbuds (e.g., components) in the physical environment.

In some embodiments, in accordance with a determination that therespective selectable item corresponds to only a single component, theelectronic device displays (1302 e), on the representation of the map inthe second user interface, a representation of the single component at alocation on the representation of the map corresponding to a physicallocation of the single component, such as if the list item 1210corresponded to only a tablet (and no other associated components), asingle representation of John's Tablet would be displayed on the map1204 in response to selecting that list item. For example, if theselected item of the plurality of selectable items corresponds to asingle component (e.g., an electronic device that does not correspond toa respective set of two or more associated components), the second userinterface concurrently displays a representation of the single componenton the representation of the map. In some embodiments, therepresentation of the single component is displayed at a location on therepresentation of the map that corresponds to a physical location of thesingle component.

The above-described manner of displaying a plurality of representationsof components on the representation of the map when a selectedselectable item corresponds to a set of two or more components anddisplaying a single representation of a component on the representationof the map when a selected selectable item corresponds to a singlecomponent provides an efficient way of indicating a physical location ofsingle components and multiple components, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient, which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiently.

In in some embodiments, the first input is received while the electronicdevice is displaying a second user interface, different from the userinterface, that includes a representation of a map and a list of aplurality of selectable items corresponding to a plurality of objects(1322 a), such as user interface 1202 in FIG. 12T (e.g., when the inputcorresponding to the request to locate a first component is received,the electronic device is displaying a user interface that includes arepresentation of a map and one or more selectable items that correspondto objects that can be located or found using the finding processesdescribed herein). In some embodiments, the one or more selectable itemsare items in a list. In some such embodiments, when a respectiveselectable item is selected in the list, a graphical (or textualrepresentation) of the component corresponding to the selected item isdisplayed at a location on the representation of the map correspondingto a physical location of the component.

In some embodiments, while displaying the second user interface andbefore receiving the first input, the electronic device receives (1322b), via the one or more input devices, a second input selecting arespective selectable item of the list of the plurality of selectableitems, such as touch contact 1226 selecting one of list items 1208-1214in FIG. 12T (e.g., before the input corresponding to the request todisplay information for locating the first component is received,receiving a selection of one of the selectable items). In someembodiments, in response to receiving the second input (1322 c), inaccordance with a determination that the respective selectable itemcorresponds to a respective set of two or more associated component(1322 d) (e.g., the components in the respective set are part of a pairof input and/or output devices, such as left and right earbuds that canbe located independently of each other), (e.g., while maintainingdisplay of the respective selectable item in the second user interface,)the electronic device displays (1322 e), in the list of the plurality ofselectable items, a plurality of selectable child items (e.g., sub-itemsof the respective selectable item) corresponding to components in therespective set of two or more associated components, such as touchcontact 1226 selecting list item 1226 in FIG. 12T and in response, inFIG. 12U, displaying child items 1252 and 1254.

For example, when a selectable item that corresponds to a respective setof two or more associated components is selected, the components in therespective set are displayed as child items of the selected item (e.g.,sub items) in the list. In some embodiments, when the respectiveselectable item corresponds to a single component, information forlocating the item is optionally displayed as child items or is displayedin a different user interface (e.g., a new user interface that causesthe display of the list of the plurality of selectable items to ceasedisplaying in the second user interface). In some embodiments, theselectable item corresponding to a respective set of two or morecomponents includes information such as a charge level for therespective set, information about the physical location of therespective set, a name of the respective set, a graphical representationof the respective set, and/or the last time the electronic devicedirectly and/or indirectly received an indication of the physicallocation of the respective set. In some embodiments, in response to aselection of the selectable item corresponding to the respective set,child items are displayed proximate to (e.g., within a thresholddistance of) the respective selectable item. In some embodiments, thechild items are selectable to initiate a process to locate the componentthat corresponds to that particular child item and include informationsuch as information about a location of the corresponding component withrespect to a user (e.g., of the electronic device), a graphicalrepresentation of the corresponding component, and/or a name of thecorresponding component. In some embodiments, child items of arespective set optionally include information similar to the informationincluded in a selectable item corresponding to the respective set (e.g.,a charge level for a corresponding component, information about thephysical location of a corresponding component, a name of thecorresponding component, a graphical representation of the correspondingcomponent, and/or the last time the electronic device directly and/orindirectly received an indication of the physical location of thecorresponding component). In some embodiments, the child items of arespective set are not displayed until the selectable item correspondingto the respective set is selected by a user.

The above-described manner of displaying child items corresponding tocomponents in a respective set of two or more associated components whenan item corresponding a set of two or more component is selectedprovides an efficient way of displaying information about the componentsin the set of two or more components, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the first input is received while the electronicdevice is displaying a second user interface, different from the userinterface, that includes a representation of a map and a list of aplurality of selectable items corresponding to a plurality of objects(1324 a) (e.g., when the input corresponding to the request to locate afirst component is received, the electronic device is displaying a userinterface that includes a representation of a map and one or moreselectable items that correspond to objects that can be located or foundusing the finding processes described herein). In some embodiments, theone or more selectable items are items in a list. In some suchembodiments, when a respective selectable item is selected in the list,a graphical (or textual representation) of the component correspondingto the selected item is displayed at a location on the representation ofthe map corresponding to a physical location of the component. In someembodiments, while displaying the second user interface and beforereceiving the first input, the electronic device receives (1324 b), viathe one or more input devices, a second input selecting a respectiveselectable item of the list of the plurality of selectable items (e.g.,before the input corresponding to the request to display information forlocating the first component is received, receiving a selection of oneof the selectable items).

In some embodiments, in response to receiving the second input (1324 c),in accordance with a determination that the respective selectable itemcorresponds to a respective set of two or more associated components(e.g., the components in the respective set are part of a pair of inputand/or output devices, such as left and right earbuds that can belocated independently of each other), in accordance with a determinationthat the two or more components are within a threshold distance (e.g.,1, 3, 6, 12, 24, 48, 96, 192 inches) of each other, (e.g., ceasingdisplay of the plurality of selectable items in the second userinterface, and while maintaining display of the map in the second userinterface,) the electronic device displays (1324 e), via the displaygeneration component, one or more options associated with locatingcomponents in the respective set of two or more associated components,such as such as touch contact 1226 selecting list item 1226 in FIG. 12Band in response, in FIG. 12C, displaying card 1228 because John's Leftand Right Earbuds are together. For example, if the selected itemcorresponds to a respective set of two or more associated components andthose components are at physical locations that are within a thresholddistance from each other, the second user interface displays options forlocating and finding the (e.g., set of) components. In some embodiments,the options include selectable options for initiating a process todisplay directions to a respective component or the set of componentsand/or to initiate a process to play a sound at a respective componentor the set of components. In some embodiments, selecting the respectiveselectable option causes a disambiguation user interface (e.g., dialogbox overlaid the second user interface) that includes selectable objectscorresponding to components in the respective set, which when selected,causes directions to that selected respective component to be displayedin the second user interface and/or a sound to be played at thatrespective component. In some embodiments, the components are determinedto be within a threshold distance of each other when the components areable to connect to each other via Bluetooth or other wirelesscommunication protocol (e.g., are located 30 or less feet away from eachother), and are determined to be farther than the threshold distance ofeach other when the components are not able to connect to each other viaBluetooth or other wireless communication protocol.

In some embodiments, in accordance with a determination that the two ormore components are not within the threshold distance of each other,(e.g., while maintaining display of the respective item,) the electronicdevice displays (13240 a plurality of selectable child itemscorresponding to components in the respective set of two or moreassociated components such as touch contact 1226 selecting list item1226 in FIG. 12T and in response, in FIG. 12U, displaying child items1252 and 1254 because John's Left and Right Earbuds are not together.For example, if the selected item corresponds to a respective set of twoor more associated components and those components are at physicallocations that are more than a threshold distance from each other, thesecond user interface displays the components of the respective set aschild items (e.g., sub items of the respective selectable item). In someembodiments, the selectable child items are displayed within a thresholddistance of the list item in which it relates (e.g., the respectiveselected item). In some embodiments, the child items are selectable toinitiate a process to locate the component that corresponds to thatparticular selected child item and includes information such asinformation about a location of the corresponding component with respectto a user (e.g., of the electronic device or the electronic deviceitself), a graphical representation of the corresponding component,and/or a name of the corresponding component.

The above-described manner of displaying finding information when thecomponents of a respective set are together and displaying child itemswhen the components of the respective set are not together provides anefficient way of indicating information about locations of thecomponents in the respective set, without a user needing to view thelocations of the components in a map, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

In some embodiments, the plurality of selectable child items include afirst item corresponding to a first component in the respective set anda second item corresponding to a second component in the respective set,different from the first component, the first item includes informationabout a location of the first component relative to the electronicdevice, and the second item includes second information about thelocation of the second component relative to the electronic device,different from the location of the first component relative to theelectronic device (1326 a), such as labels 1256 and 1258 in FIG. 12U.For example, the child item corresponding to the first componentindicates how far (e.g., in feet, yards, miles, etc.) and/or thedirection the first component is from the electronic device. Similarly,the child item corresponding to the second component indicates how far(e.g., in feet, yards, miles, etc.) and/or the direction the secondcomponent is from the electronic device.

The above-described manner of displaying information about a location ofa corresponding component relative to the electronic device in arespective child item provides an efficient way of indicating a currentrelative location of the first component and with respect to theelectronic device, which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient, whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiently.

In some embodiments, the first input is received while the electronicdevice is displaying a second user interface, different from the firstuser interface, that includes a representation of a map and a list of aplurality of selectable items corresponding to a plurality of objects(1328 a) (e.g., when the input corresponding to the request to locate afirst component is received, the electronic device is displaying a userinterface that includes a representation of a map and one or moreselectable items that correspond to objects that can be located or foundusing the finding processes described herein). In some embodiments, theone or more selectable items are items in a list. In some suchembodiments, when a respective selectable item is selected in the list,a graphical (or textual representation) of the component correspondingto the selected item is displayed at a location on the representation ofthe map corresponding to a physical location of the component. In someembodiments, while displaying the second user interface and beforereceiving the first input, the electronic device receives (1328 b), viathe one or more input devices, a second input selecting a respectiveselectable item of the list of the plurality of selectable items (e.g.,before the input corresponding to the request to display information forlocating the first component is received, receiving a selection of oneof the selectable items).

In some embodiments, in response to receiving the second input (1328 c),in accordance with a determination that respective selectable itemcorresponds to a respective set of two or more components (e.g., thecomponents in the respective set are communicatively coupled (e.g.,paired together)) and that the two or more components are within athreshold distance of each other, the electronic device displays (1328d), on the representation of the map in the second user interface, arepresentation of the respective set of two or more associatedcomponents at a location on the representation of the map correspondingto a physical location of the two or more associated components, such asin FIGS. 12B and 12C, because John's Left and Right Earbuds are togetherthe selection of list item 1208 in FIG. 12B causes the display of asingle representation of John's Earbuds in FIG. 12C. For example, if thetwo or more components in the respect set are within a thresholddistance of each other, a single representation corresponding to therespective set is displayed on the representation of the map. In someembodiments the components determined to be together, if the physicallocation of the components are less than 10 feet, 5 feet, 3 feet, or 1foot, etc. apart. In some embodiments, the two or more components arewithin a threshold distance of each other if components are able to bepaired together via a Bluetooth connection. In some embodiments, therepresentation of the respective set includes a graphical representationof the respective set, a name of the respective set, etc. In someembodiments, the representation of the respective set is selectable todisplay information about the respective set and/or one or moreselectable objects that are selectable to initiate a process to locateone or more of (or the set of) the components in the respective set orplay a sound at one or more of (or the set of) the components.

In some embodiments, in accordance with a determination that respectiveselectable item corresponds to a respective set of two or morecomponents and that the two or more components are not within thethreshold distance of each other, the electronic device concurrentlydisplays (1328 e), on the representation of the map in the second userinterface, a plurality of representations of components corresponding tocomponents in the respective set of two or more associated components atlocations on the representation of the map corresponding to physicallocations of the two or more associated components, such as touchcontact 1226 selecting list item 1226 in FIG. 12T and in response, inFIG. 12U, displaying child items 1252 and 1254 because John's Left andRight Earbuds are not together. For example, if the two or morecomponents in the respect set are not within a threshold distance ofeach other, a plurality of representations corresponding to componentsin the respective set are displayed (e.g., at different locations) onthe representation of the map. In some embodiments, the components aredetermined to not be within a threshold distance of each other if thephysical locations of the components are more than 10 feet, 5 feet, 3feet, or 1 foot, etc. apart. In some embodiments, the two or morecomponents are determined to not be within a threshold distance of eachother if the components are unable to be paired together via a Bluetoothconnection. In some embodiments, the representation of the respectiveincludes a graphical representation of the respective set, a name of therespective set, etc. In some embodiments, the plurality ofrepresentations are selectable to display information about thecomponent it corresponds to and/or one or more selectable objects thatare selectable to initiate a process to locate one or more of thecomponents in the respective set or play a sound at one or more of thecomponents.

The above-described manner of displaying a plurality of representationscorresponding to components in a respective set if the component areseparated and displaying a single representation if the componentscorresponding to the respective set are together provides an efficientway of indicating the location of the components in the respective set,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient, which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiently.

In some embodiments, the electronic device displays (1323 a) the userinterface for locating the second component of the first set of two ormore components in response to receiving the indication that the firstcomponent has been located is in accordance with a determination thatthe second component is not already located (e.g., if the secondcomponent is not in a charging state, is not being worn by a user, isnot inside of a case, or is not otherwise indicated as being found). Insome embodiments, in response to receiving the indication that the firstcomponent has been located (1330 b), in accordance with a determinationthat the second component in the first set of two or more components isalready located, the electronic device forgoes (1330 c) displaying theuser interface for locating the second component of the set of two ormore components, such as if the left earbud is already located when theright earbud was found in FIG. 1211, device 500 would not displayfinding information for John's Left earbud. For example, if the secondcomponent is indicated as being located (e.g., if the second componentis in a charging state, inside of a case associated with the secondcomponent, is being worn by a user), the user interface for locating thesecond component is not displayed by the electronic device. In someembodiments, the second component is indicated as already being locatedif a user has manually indicated that the second component has beenlocated. In some embodiments, if the second component has already beenindicated as located, the electronic device displays a user interfacefor locating a third component of the set of two or more components. Insome embodiments, if no components in the set of components remains notlocated, the electronic device optionally ceases displaying the userinterface for locating one or more components of the set of components.

The above-described manner of displaying a user interface for locatingthe second component when the second component is not already locatedand not displaying the user interface for locating the second componentwhen the second component is already located provides an efficient wayof displaying information for locating the second component when thesecond component is not already found, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 13A-13J have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700, 900, 1100 and 1500) are also applicable in an analogousmanner to method 1300 described above with respect to FIGS. 13A-13J. Forexample, the map and finding user interfaces described above withreference to method 1300 optionally have one or more of thecharacteristics of device or object tracking, finding user interfaces,map user interfaces, separation alerts, etc., described herein withreference to other methods described herein (e.g., methods 700, 900,1100 and 1500). For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., a as described with respect to FIGS. 1A-1B, 3, 5A-5H)or application specific chips. Further, the operations described abovewith reference to FIGS. 13A-13J are, optionally, implemented bycomponents depicted in FIGS. 1A-1B. For example, displaying operation1302 e, receiving operations 1302 a and 1302 c, and updating operation1302 b are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch screen 504, and event dispatcher module174 delivers the event information to application 136-1. A respectiveevent recognizer 180 of application 136-1 compares the event informationto respective event definitions 186, and determines whether a firstcontact at a first location on the touch screen corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 14A-14I illustrate exemplary ways in which an electronic devicefacilitates display of location information of associated componentsthat are at one or more physical locations in accordance with someembodiments of the disclosure. The embodiments in these figures are usedto illustrate the processes described below, including the processesdescribed with reference to FIGS. 15A-15E.

FIG. 14A illustrates an exemplary device 500 that includes touch screen504. In FIG. 14A, the electronic device 500 is displaying user interface1402. User interface 1402 includes a list 1406 of devices or objectswhose location can be tracked/viewed by device 500, such as list item1410 corresponding to John's Tablet, list item 1414 corresponding toJohn's Computer. The list 1406 also includes representations ofcomponents that are associated with each other, such as list item 1408corresponding to John's Earbuds (e.g., corresponding to a left earbud, aright earbud and a charging case for the earbuds that are associatedwith each other), and list item 1412 corresponding to John's Phone &Wallet (e.g., corresponding to a smartphone and associated walletaccessory that is physically attached to the phone, such as via amagnetic attachment mechanism). In the example of FIG. 14A, list items1408-1414 include a name of the object that corresponds to the list item(“John's Earbuds”, “John's Tablet”, etc.), a graphical representation ofthat object, labels which provide textual descriptions about the lasttime device 500 received information about a location of that object,and information about the last known location for that object.

Additionally, user interface 1402 also includes a representation of amap 1404. The representation of the map 1404 includes representations ofdevices or objects whose location can be tracked/viewed by device 500,and also includes representations of components that are associated witheach other, such as a representation of John's Earbuds 1416 displayed ata location on map 1404 corresponding to the last known location forJohn's Earbuds, a representation of John's Tablet 1422 displayed at alocation on map 1404 corresponding to the last known location for John'sTablet, a representation of John's Computer 1420 displayed at a locationon map 1404 corresponding to the last known location for John'sComputer, and a representation of John's Phone & Wallet 1418 displayedat a location on map 1404 corresponding to the last known location forJohn's Phone & Wallet. The representation of the map 1404 also includesa location indicator 1424 that indicates a location of the electronicdevice 500.

In FIG. 14B, while displaying user interface 1402, the electronic device500 receives a selection of list item 1408 corresponding to John'sEarbuds (indicated by touch contact 1403). As will be discussed indetail later, in some embodiments, based on whether the components(e.g., the left earbud, the right earbud and/or the charging case)associated with the selected list item are currently together orseparated will result in different responses by device 500 when thatlist item is selected. In the example of FIG. 14B, John's Earbudsinclude a left earbud, a right earbud and a charging case that are at asame physical location (e.g., are not separated from one another). Insome embodiments, the left earbud, right earbud and charging case areconsidered to be in the same location if the earbuds and charging caseare within a threshold distance of each other (e.g., 0.1, 0.3, 0.5, 1,3, 5, 10 or 20 yards) and/or if the earbuds are both located in the sameobject (e.g., the charging case).

In FIG. 14C, because the left earbud, right earbud and charging case ofJohn's Earbuds are at a same physical location, in response to the inputin FIG. 14B, user interface 1402 is updated to display a card userinterface 1428 corresponding to John's Earbuds. Specifically, card userinterface 1428 includes label 1434 indicating the object that isassociated with card user interface 1428 (“John's Earbuds”), label 1436that provides information about the last known location of John'sEarbuds and the last time the device 500 received location informationfor John's Earbuds (“Near Mission Ave, Last Seen 6m ago”), andselectable options 1430 and 1432 corresponding to functions availablefor finding John's Earbuds, as described in more detail with referenceto methods 900, 1100 and/or 1300. Additionally, the representation ofJohn's Earbuds 1416 is focused (e.g., centered) in the representation ofthe map 1404, and device 500 ceases to display representation of other,unselected items in map 1404. Because the left earbud, right earbud andcharging case were determined to be in a same physical location when theselection input 1403 was received in FIG. 14B, the representation ofJohn's Earbuds 1416 is displayed as a single combined representation inthe representation of the map 1404 (as compared to displaying separaterepresentations for the left earbud, right earbud and/or charging casewhen the earbuds are not in the same physical location, as will bedescribed later with reference to FIGS. 14D-14I).

In FIG. 14D, device 500 is displaying user interface 1402 as describedpreviously with reference to FIG. 14A; however, in FIG. 14D, the leftearbud of John's Earbuds is separated from the right earbud and chargingcase of John's Earbuds. As a result, device 500 is displaying a separaterepresentation 1419 of the left earbud on the representation of the map1404 at a location corresponding to the location of the left earbud, anda separate representation 1417 of the right earbud and charging case onthe representation of the map 1404 at a location corresponding to thelocation of the right earbud and charging case.

In FIG. 14D, device 500 detects selection of list item 1408corresponding to John's Earbuds, such as via a tap of contact 1403. Inresponse, because the left earbud is separated from the right earbud andcharging case, and because the right earbud and charging case are notseparated from each other (e.g., the right earbud is placed within thecharging case), in FIG. 14E device 500 updates list 1406 to includeseparate list items 1452 and 1454 corresponding to the left earbud andthe right earbud/charging case, respectively. For example, list item1452 includes label “Left Earbud” indicating that the list itemcorresponds to the left earbud, and list item 1454 includes label “RightEarbud, Case” indicating that the list item corresponds to the rightearbud and the charging case. Further, list item 1452 includes distanceand time information 1458 for the left earbud analogous to as describedwith reference to list items 1408-1414, and list item 1454 includesdistance and time information 1456 for the right earbud and chargingcase analogous to as described with reference to list items 1408-1414.In FIG. 14E, because John's Phone & Wallet corresponds to a collectionof components different from John's Earbuds, device 500 maintains theseparate list item 1412 for the collection of John's Phone & Wallet—andcorresponding representation 1418 on map 1404—in user interface 1402even if John's Phone & Wallet is/are in proximity to one or morecomponents of John's Earbuds.

FIG. 14F illustrates an alternative to FIG. 14E in response to the inputdetected in FIG. 14D if the left earbud, the right earbud, and thecharging case of John's Earbuds are all separated from each other. Asshown in FIG. 14F, in response to the input in FIG. 14D, device 500 hasupdated list 1406 in user interface 402 to additionally include listitem 1455 corresponding to the right earbud, and list item 1460corresponding to the charging case (in addition to list item 1452corresponding to the left earbud, as previously described). For example,list item 1455 includes label “Right Earbud” indicating that the listitem corresponds to the right earbud, and list item 1460 includes label“Case” indicating that the list item corresponds to the charging case.Further, list item 1455 includes distance and time information 1457 forthe right earbud analogous to as described with reference to list items1408-1414, and list item 1460 includes distance and time information1462 for the charging case analogous to as described with reference tolist items 1408-1414. Device 500 is also displaying separaterepresentations of the left earbud 1419, the right earbud 1421, and thecharging case 1423 at locations on map 1404 corresponding to thelocations of those components. Similar to as described above, in FIG.14F, because John's Phone & Wallet corresponds to a collection ofcomponents different from John's Earbuds, device 500 maintains theseparate list item 1412 for the collection of John's Phone & Wallet—andcorresponding representation 1418 on map 1404—in user interface 1402even if John's Phone & Wallet is/are in proximity to one or morecomponents of John's Earbuds.

In FIG. 14E or FIG. 14F, in response to selection of a list itemcorresponding to a particular component or collection of components ofJohn's earbuds, device 500 optionally displays a card user interface(e.g., similar to card user interface 1428) for the selected componentor collection of components, as will now be described. For example, inFIG. 14F, device 500 detects selection of list item 1455, such as via atap of contact 1403.

In response, in FIG. 14G, device 500 displays card user interface 1470corresponding to the right earbud. Card user interface 1470 optionallyincludes item label 1472, location and time information 1474, selectableoption 1476 and selectable option 1478 that are analogous tocorresponding elements described with reference to card user interface1428 in FIG. 14C, but instead directed to the right earbud in particularrather than the collection of the right and left earbuds and thecharging case. In addition to displaying card user interface 1470,device 500 updates display of map 1404 to no longer includerepresentations of items that are not part of the left earbud/rightearbud/charging case collection of items. For example, despiterepresentation 1418 (corresponding to John's Phone & Wallet) beingdisplayed at a location on map 1404 in FIG. 14F that remains displayedin FIG. 14G, device 500 no longer displays representation 1418 in FIG.14G. In contrast, device 500 in FIG. 14G continues to displayrepresentation 1423 corresponding to the charging case on map 1404(e.g., at a location on map 1404 corresponding to the location of thecharging case) despite card user interface 1470 being associated withthe right earbud (e.g., and not associated with the charging case),because the charging case is part of the collection of components thatis associated with the right earbud (e.g., the left earbud, the rightearbud, and the charging case).

FIG. 14H illustrates an alternative to FIG. 14F. In FIG. 14H, userinterface 1402 includes list 1406 as described with reference to FIG.14E. In FIG. 14H, device 500 detects selection of list item 1454corresponding to the right earbud and the charging case, such as via atap of contact 1403. In response, in FIG. 141, device 500 displays carduser interface 1480 corresponding to the right earbud and charging casecombination. Card user interface 1480 optionally includes item label1482, location and time information 1484, selectable option 1486 andselectable option 1488 that are analogous to corresponding elementsdescribed with reference to card user interface 1428 in FIG. 14C andcard user interface 1470 in FIG. 14G, but instead directed to the rightearbud and charging case combination in particular. In addition todisplaying card user interface 1480, device 500 updates display of map1404 to no longer include representations of items that are not part ofthe left earbud/right earbud/charging case collection of items andoptionally focuses (e.g., centers) display of map 1404 on representation1417 of the right earbud/charging case combination, thus causingrepresentation 1419 of the left earbud to no longer be in view on map1404. Further, because the combination of components associated withcard user interface 1480 includes the charging case, selectable option1488 is optionally selectable to cause device 500 to initiate a processto play sound from the charging case (optionally rather than the rightearbud) to aid a user in finding the right earbud and the charging case.In some embodiments, the charging case has a larger battery and/orspeaker than the right earbud, thus making its speaker a preferredspeaker for generating audio that is more likely to be heard by the userwhen searching for the right earbud and/or charging case.

FIGS. 15A-15E are flow diagrams illustrating a method 1500 offacilitating display of location information of associated componentsthat are at one or more physical locations in accordance with someembodiments, such as in FIGS. 14A-141. The method 1500 is optionallyperformed at an electronic device such as device 100, device 300, ordevice 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4Band 5A-5H. Some operations in method 1500 are, optionally combinedand/or order of some operations is, optionally, changed.

As described below, the method 1500 provides ways to display locationinformation of associated components that are at one or more physicallocations. The method reduces the cognitive burden on a user wheninteracting with a user interface of the device of the disclosure,thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, increasing the efficiency of theuser's interaction with the user interface conserves power and increasesthe time between battery charges.

In some embodiments, method 1500 is performed at an electronic device incommunication with a display generation component and one or more inputdevices. In some embodiments, the electronic device has one or more ofthe characteristics of the electronic devices of methods 700, 900, 1100and/or 1300. In some embodiments, the display generation component andone or more of the characteristics of the display generation componentsof methods 700, 900, 1100 and/or 1300. In some embodiments, the one ormore input devices have one or more of the characteristics of the inputdevices of methods 700, 900, 1100 and/or 1300.

In some embodiments, the electronic device receives (1502 a), via theone or more input devices, a first input (e.g., an input such as a touchinput, mouse input and/or keyboard input) corresponding to a request tolocate one or more components of a first set of two or more componentsthat are paired together, such as an input to display user interface1402 in FIG. 14A. For example, receiving an input to display and/orlaunch an item locating application (e.g., selection of an icon for theitem locating application on a home screen user interface such asdescribed with reference to FIG. 4A) that displays informationassociated with the locations of one or more items to which theelectronic device has access, including the first set of two or morecomponents that are paired together. In some embodiments, the first setof two or more components has one or more of the characteristics of thesets of two or more (paired) components described with reference tomethods 900 and/or 1300.

In some embodiments, in response to receiving the first input, theelectronic device displays (1502 b), via the display generationcomponent in an item locating user interface (e.g., a user interface ofan item locating application installed on the electronic device), acombined representation of the first set of components, such as listitem 1408 in user interface 1402 in FIG. 14A. For example, the itemlocating user interface optionally includes representations of one ormore different items, to which the locations of which the electronicdevice has access (e.g., via wired or wireless communication directlywith the one or more different items, or indirect wired or wirelesscommunication with the one or more different items via one or more otherelectronic devices, some of which are optionally in direct wired orwireless communication with the one or more different items). In someembodiments, the item locating user interface includes a representationof a map, and the representation of the map includes representations ofthe one or more different items (e.g., including the first set ofcomponents) at locations on the representation of the map correspondingto the locations of the one or more different items. In someembodiments, the item locating user interface includes a list of one ormore different items (e.g., including the first set of components), andthe list includes representations of the one or more different itemsdisplayed along with indications of the locations of the one or moredifferent items (e.g., indications of addresses, indications ofdistances from the electronic device, and/or indications of cities orcountries in which the items are located). The item locating userinterface optionally includes a single representation of the first setof components, without including separate representations for individualcomponents of the first set of components. In some embodiments, thecombined representation of the first set of components includes aphotorealistic or otherwise image of the collection of the first set ofcomponents (e.g., an image of two earbuds inside a case in a scenario inwhich the components of the first set of components are a left earbud, aright earbud, and the case). In some embodiments, if the first inputwere an input corresponding to a request to locate one or morecomponents that are not paired together, the item locating userinterface would optionally include separate representations (e.g., on amap and/or in a list) of the one or more components, rather than acombined representation as described above. Such separaterepresentations would optionally be selectable to display additionalinformation associated with locating the respective componentcorresponding to the selected representation, similar to as describedbelow.

In some embodiments, while displaying the combined representation of thefirst set of components, the electronic device receives (1502 c), viathe one or more input devices, a second input corresponding to selectionof the combined representation of the first set of components, such asselection of list item 1408 in FIG. 14B (e.g., an input such as a touchinput, mouse input, and/or keyboard input).

In some embodiments, in response to receiving the second input, theelectronic device displays (1502 d), via the display generationcomponent, additional information associated with locating the one ormore components of the first set of components, such as shown in FIGS.14C, 14E or 14F. In some embodiments, the additional informationincludes information for locating one or more components of the firstset of components, as will be described in more detail below. In someembodiments, the additional information includes one or more selectableoptions that are selectable to initiate a process to locate one or morecomponents of the first set of components, as will be described in moredetail below. Displaying a combined representation for a set ofcomponents in an item locating user interface reduces unnecessaryconsumption of user interface area and facilitates efficient locatinginteractions with the set of components.

In some embodiments, displaying the additional information associatedwith locating the one or more components of the first set of componentsincludes (1504 a) in accordance with a determination that the first setof components are in proximity to one another, such as the left andright earbuds and the charging case in FIG. 14B being in proximity toone another (e.g., the components that make up the first set ofcomponents are all within a threshold distance of one another, such as0.1, 0.3, 0.5, 1, 3, 5, 10 or 20 yards and/or otherwise havecharacteristics relative to one another that would not trigger aseparation alert with respect to one another as described with referenceto method 900), displaying (1504 b), via the display generationcomponent, a second user interface associated with the first set ofcomponents, such as user interface 1428 in FIG. 14C (e.g., a userinterface dedicated to the first set of components), wherein the seconduser interface includes one or more selectable options for performingone or more finding operations for the combined first set of components,such as option 1430 and 1432 in FIG. 14C (e.g., such as options 1232 and1230 described with reference to FIG. 12C). For example, the second userinterface is optionally a user interface displayed in an item locatingapplication that includes information about the current location of thefirst set of components (e.g., an address or city), an indication ofwhen the location of the first set of components was last updated,and/or one or more selectable options for initiating processes to locatethe first set of one or more components, such as described withreference to user interface 1228 in FIG. 12C. Displaying a userinterface for the combined set of components when the components are inproximity to one another facilitates efficient locating interactionswith the set of components.

In some embodiments, displaying the additional information associatedwith locating the one or more components of the first set of componentsincludes (1506 a) in accordance with a determination that at least onecomponent of the first set of components is not in proximity to at leastone other component of the first set of components (1506 b), such as theleft earbud not being in proximity to the right earbud/charging case inFIG. 14D (e.g., the components that make up the first set of componentsare not all within a threshold distance of one another, such as 0.1,0.3, 0.5, 1, 3, 5, 10 or 20 yards and/or otherwise have characteristicsrelative to one another that would trigger a separation alert withrespect to one another as described with reference to method 900. Forexample, the at least one component is more than the threshold distancefrom other(s) of the set of components), displaying, in the itemlocating user interface a first representation of first one or morecomponents in the first set of components (1506 c), such as list item1452 in FIG. 14E (e.g., the at least one component that is more than thethreshold distance from other(s) of the set of components), and a secondrepresentation of second one or more components in the first set ofcomponents (1506 d), such as list item 1454 in FIG. 14E (e.g., theother(s) of the set of components that are within the threshold distanceof one another), wherein the first one or more components are not inproximity to the second one or more components. For example, theelectronic device optionally displays separate representations forcomponents (or groups of components) of the set of components that arenot in proximity to at least one other component in the set ofcomponents. In some embodiments, the components included in a givengroup of one or more components (corresponding to a singlerepresentation that is displayed) are those components in the set ofcomponents that are in proximity to one another. For example, theelectronic device transitions from displaying representation 1208 inFIG. 12T to representations 1252 and 1254 in FIG. 12U. Displayingdifferent representations for different similarly-situated individual orgroups of components facilitates efficient locating interactions withthose similarly-situated individual or groups of components.

In some embodiments, while displaying, in the item locating userinterface, the first representation and the second representation, theelectronic device receives (1508 a), via the one or more input devices,a third input corresponding to selection of a respective representationof a respective component, such as the selection from contact 1403 inFIG. 14F or FIG. 14H (e.g., an input such as a touch input, mouse input,and/or keyboard input). In some embodiments, in response to receivingthe third input (1508 b), in accordance with a determination that thethird input corresponds to selection of the first representation of thefirst one or more components, the electronic device displays (1508 c),via the display generation component, a second user interface associatedwith the first one or more components, such as user interface 1470 inFIG. 14G (e.g., a user interface dedicated to the first one or morecomponents), wherein the second user interface includes one or moreselectable options for performing one or more finding operations for thefirst one or more components, such as options 1476 and 1478 in FIG. 14G(e.g., such as options 1232 and 1230 described with reference to FIG.12C, but for the first one or more components) but does not include aselectable option for performing a finding operation for the second oneor more components, such as user interface 1470 in FIG. 14G notincluding options for finding the left earbud or the charging case(e.g., does not include an analogous option 1232 or 1230 for the secondone or more components). For example, the second user interface isoptionally a user interface displayed in an item locating applicationthat includes information about the current location of the first one ormore components (e.g., an address or city), an indication of when thelocation of the first one or more components was last updated, and/orone or more selectable options for initiating processes to locate thefirst one or more components, similar to as described with reference touser interface 1228 in FIG. 12C. However, the second user interfaceoptionally does not include information about the current location ofthe second one or more components (e.g., an address or city), anindication of when the location of the second one or more components waslast updated, and/or one or more selectable options for initiatingprocesses to locate the second one or more components.

In some embodiments, in accordance with a determination that the thirdinput corresponds to selection of the second representation of thesecond one or more components, such as the selection from contact 1403in FIG. 14H, the electronic device displays (1508 d), via the displaygeneration component, a third user interface associated with the secondone or more components, such as user interface 1480 in FIG. 14I (e.g., auser interface dedicated to the second one or more components), whereinthe third user interface includes one or more selectable options forperforming one or more finding operations for the second one or morecomponents, such as options 1486 and 1488 in FIG. 141 (e.g., such asoptions 1232 and 1230 described with reference to FIG. 12C, but for thesecond one or more components) but does not include a selectable optionfor performing a finding operation for the first one or more components,such as user interface 1480 in FIG. 141 not including options forfinding the left earbud (e.g., does not include an analogous option 1232or 1230 for the first one or more components). For example, the thirduser interface is optionally a user interface displayed in an itemlocating application that includes information about the currentlocation of the second one or more components (e.g., an address orcity), an indication of when the location of the second one or morecomponents was last updated, and/or one or more selectable options forinitiating processes to locate the second one or more components,similar to as described with reference to user interface 1228 in FIG.12C. However, the third user interface optionally does not includeinformation about the current location of the first one or morecomponents (e.g., an address or city), an indication of when thelocation of the first one or more components was last updated, and/orone or more selectable options for initiating processes to locate thefirst one or more components. Displaying different item locating userinterface for different similarly-situated individual or groups ofcomponents avoids erroneous finding interactions with incorrect items orgroups of items and facilitates efficient finding operations forsimilarly-situated individual or groups of components.

In some embodiments, the second user interface includes a representationof a map (e.g., a map that encompasses a region that includes thelocation of the first one or more components) and a representation ofthe first one or more components displayed at a location on the mapcorresponding to a location of the first one or more components (1510a), such as map 1404 in FIG. 14G including representation 1421 of theright earbud (e.g., an icon, image or graphic of the collection of firstone or more components displayed at a location on the map correspondingto the determined location of the first one or more components, such asdisplayed at an intersection of two roads if that is the determinedlocation for the first one or more components). In some embodiments, inaccordance with a determination that a location of the second one ormore components is included in a region corresponding to therepresentation of the map (e.g., if the physical region of the mapincludes the determined location of the second one or more components),the second user interface includes a representation of the second one ormore components displayed at a location on the map corresponding to thelocation of the second one or more components (1510 b), such asrepresentation 1423 of the charging case shown on map 1404 in FIG. 14G(e.g., an icon, image or graphic of the collection of second one or morecomponents displayed at a location on the map corresponding to thedetermined location of the second one or more components, such asdisplayed at an intersection of two roads if that is the determinedlocation for the second one or more components). Thus, in someembodiments, even though the second user interface is not associatedwith the second one or more components, if the location of the secondone or more components happens to fall within the displayed area of themap, the electronic device displays a representation of the second oneor more components in the displayed area of the map. The electronicdevice optionally similarly displays a representation of the first oneor more components in the displayed area of the map in the third userinterface if the location of the first one or more components fallswithin the displayed area of the map in the third user interface.Displaying a representation of the second one or more components in thesecond user interface reduces the number of inputs needed to displayinformation about the location of the second one or more components whenthe second one or more components are relatively close to the first oneor more components.

In some embodiments, the first one or more components is a singlecomponent (1512), such as left earbud corresponding to list item 1452 inFIG. 14E (e.g., a left earbud of a pair of left and right earbuds). Forexample, a single component of the first set of components is separatedfrom others of the first set of components, and the electronic devicedisplays a representation of that single component. Selection of therepresentation of that single component optionally causes the electronicdevice to display a user interface associated with that singlecomponent, as previously described. Displaying a representation of asingle component of the set of components facilitates efficient locatinginteractions with the single component and indicates, without furtherinput, that the single component is separated from the others of the setof components.

In some embodiments, the second one or more components includes a firstcomponent and a second component of the first set of components, and thefirst component is in proximity to the second component (1514), such asthe right earbud and the charging case corresponding to list item 1454in FIG. 14E (e.g., a left earbud and a right earbud of a pairedcollection of left and right earbuds and a corresponding charging casefor the left and right earbuds). For example, a collection of componentsof the first set of components is separated from others of the first setof components, and the electronic device displays a representation ofthat collection of components. Selection of the representation of thatcollection of components optionally causes the electronic device todisplay a user interface associated with that collection of components,as previously described. In some embodiments, the second one or morecomponents are one earbud and the charging case of the paired collectionof left and right earbuds and the charging case. In some embodiments,different collections of components (e.g., having one or more of thecharacteristics of the first set of components described herein) areoptionally displayed in ways similar to as described herein with respectto the first set of components. If such a second set of components wereat the same location (e.g., as described herein) as the first set ofcomponents (e.g., the first and second set of components are inproximity to one another as described herein), the electronic devicewould optionally not combine representations of one or more componentsof the second set of components with representations of one or morecomponents of the first set of components. Rather, the electronic devicewould optionally display representations of one or more components ofthe second set of components in one or more of the manners as describedherein with reference to the first set of components, and separatelyfrom representations of the first set of components. Further, in someembodiments, components (e.g., earbuds and/or charging cases) that arenot associated with one another (e.g., because they are not pairedtogether and/or are associated with different sets ofcomponents/earbuds, instead) will not be displayed with combinedrepresentations (e.g., as described herein), even if they are inproximity to one another (e.g., as described herein). Thus, in someembodiments, components from different sets of components that are notassociated with each other are optionally not combined by the electronicdevice into combined representations, even if one or more or all of theother requirements for being displayed in a combined representation aresatisfied. Displaying a representation of a collection of components ofthe set of components facilitates efficient locating interactions withthe collection of components and indicates, without further input, thatthe collection of components is separated from the others of the set ofcomponents.

In some embodiments, the first set of components includes a firstwireless headphone (e.g., left earbud) and a second wireless headphone(e.g., right earbud) that are paired together (1516), such as the leftand right earbuds described with reference to FIGS. 14A-14I (e.g., suchas described with reference to methods 900, 1100 and/or 1300).Performing the various locating-related operations and/or displaying thevarious locating-related user interfaces described herein for pairedwireless headphones facilitates efficient locating interactions for suchheadphones, which are optionally more likely to be separated from oneanother due to their wireless connection with each other (e.g., asopposed to wired connection).

In some embodiments, the first set of components includes a firstwireless headphone (e.g., left earbud), a second wireless headphone(e.g., right earbud), and a charging case for the first wirelessheadphone and the second wireless headphone that are paired with eachother (1518), such as the left and right earbuds and the charging casedescribed with reference to FIGS. 14A-14I (e.g., such as described withreference to methods 900, 1100 and/or 1300). For example, the chargingcase is configured to store the first and second wireless headphones,and while both or either are stored in the charging case, the chargingcase charges the battery of the headphone(s) that are stored in it. Insome embodiments, the first wireless headphone, the second wirelessheadphone and the charging case are paired with each other. Performingthe various locating-related operations and/or displaying the variouslocating-related user interfaces described herein for paired wirelessheadphones and corresponding charging case facilitates efficientlocating interactions for such headphones and charging case, which areoptionally more likely to be separated from one another due to theirwireless connection with each other (e.g., as opposed to wiredconnection).

In some embodiments, the additional information associated with locatingthe one or more components of the first set of components includes aselectable option that is selectable to initiate a process to generate,at a first component of the first set of components, audio for locatingthe first set of components, such as option 1488 in FIG. 141, whereinthe first component is a charging case for one or more other componentsin the first set of components (1520). For example, the charging case isa charging case for left and/or right wireless earbuds as describedabove. In some embodiments, the additional information includes aselectable option, similar to option 1232 in FIG. 12C, that isselectable to cause the charging case to emit audio that is audible tothe user (e.g., if the user is close enough to the charging case to hearthe emitted audio) to help the user in finding the charging case. Insome embodiments, the additional information includes such an option ifthe charging case is co-located with one or more of its correspondingearbuds (e.g., the earbuds are placed in the charging case), rather thancausing audio to be emitted from the one or more co-located earbuds. Insome embodiments, the charging case is determined to be co-located withone or more of its corresponding earbuds if the earbuds are placed inthe charging case (and optionally not co-located if the earbuds are notplaced in the charging case). In some embodiments, the charging case isdetermined to be co-located with one or more of its correspondingearbuds if the earbuds are within a threshold distance (e.g., 0.01, 0.1,0.5, 1, 3, 5, 10, 20, 50 or 100 yards) of the charging case, whether ornot the earbuds are placed in the charging case (and optionally notco-located if the earbuds are further than the threshold distance fromthe charging case). In some embodiments, the charging case has a largerbattery and/or speaker than its corresponding earbuds, and therefore isable to generate louder and/or longer audio than its correspondingearbuds. Displaying an option to generate audio at the charging casefacilitates finding of the charging case, and in the case of co-locatedearbuds, increases the chances of successfully locating the earbuds dueto the ability of the charging case to generate a stronger audio output.

In some embodiments, the electronic device receives (1522 a), via theone or more input devices, a third input corresponding to a request todesignate a (current) location (of the first set of components) as atrusted location (e.g., similar to as described with reference to method900), wherein the first set of components includes a first component anda second component (e.g., the left earbud, the right earbud and/or thecharging case described with reference to FIGS. 14A-14I). For example,the third input optionally corresponds to selection of option 812 b inFIG. 8K (or selection of other similar options in FIGS. 8L-8T), but forthe first set of components. The electronic device optionally displayssuch an option for the first set of components in one or of the waysdescribed with reference to FIGS. 8A-8T and/or method 900.

In some embodiments, in response to receiving the third input, theelectronic device designates (1522 b) the (current) location (of thefirst set of components) as a trusted location for the first componentand for the second component, such as for the left earbud, the rightearbud and/or the charging case described with reference to FIGS.14A-14I (e.g., similar to as described with reference to method 900).Thus, in some embodiments, a (single) input for setting a trustedlocation for the first set of components optionally sets that trustedlocation for (each of) the components included in the first set ofcomponents. As such, after the third input is received, if theelectronic device becomes separated from the collection of components inthe first set of components, or any single component or group ofcomponents in the first set of components, and the single component orgroup of components in the first set of components is located at thetrusted location, the electronic device will optionally not generate aseparation alert (e.g., as described with reference to method 900) forthe single component or group of components in the first set ofcomponents. In some embodiments, the third input is an input directed toa single component of the first set of components. In some embodiments,the third input is an input directed to a subgroup of components of thefirst set of components. In some embodiments, the third input is aninput directed to the first set of components. Designating a location asa trusted location for multiple components in the set of componentsreduces the number of inputs needed to set trusted locations for pairedcomponents.

As described above, one aspect of the present technology is thegathering and use of data available from specific and legitimate sourcesto improve the ability for users to track and locate items or devicesthat may be of interest to them. The present disclosure contemplatesthat in some instances, this gathered data may include personalinformation data that uniquely identifies or can be used to identify aspecific person. Such personal information data can include demographicdata, location-based data, online identifiers, telephone numbers, emailaddresses, home addresses, data or records relating to a user's healthor level of fitness (e.g., vital signs measurements, medicationinformation, exercise information), date of birth, or any other personalinformation.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toidentify the location of remote locator objects and/or identify thelocation of the user. Accordingly, use of such personal information dataenables users to identify, find, and otherwise interact with remotelocator objects. Further, other uses for personal information data thatbenefit the user are also contemplated by the present disclosure. Forinstance, health and fitness data may be used, in accordance with theuser's preferences to provide insights into their general wellness, ormay be used as positive feedback to individuals using technology topursue wellness goals.

The present disclosure contemplates that those entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities would beexpected to implement and consistently apply privacy practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. Such informationregarding the use of personal data should be prominent and easilyaccessible by users, and should be updated as the collection and/or useof data changes. Personal information from users should be collected forlegitimate uses only. Further, such collection/sharing should occur onlyafter receiving the consent of the users or other legitimate basisspecified in applicable law. Additionally, such entities should considertaking any needed steps for safeguarding and securing access to suchpersonal information data and ensuring that others with access to thepersonal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations that may serve to imposea higher standard. For instance, in the US, collection of or access tocertain health data may be governed by federal and/or state laws, suchas the Health Insurance Portability and Accountability Act (HIPAA);whereas health data in other countries may be subject to otherregulations and policies and should be handled accordingly.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, such as inthe case of advertisement delivery services, the present technology canbe configured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide personal data and/or device or objectlocation data. In yet another example, users can select to limit thelength of time personal data and/or device or object location data ismaintained or entirely block the development of a baseline locationprofile. In addition to providing “opt in” and “opt out” options, thepresent disclosure contemplates providing notifications relating to theaccess or use of personal information. For instance, a user may benotified upon downloading an application that their personal informationdata and/or location data will be accessed and then reminded again justbefore personal information data is accessed by the application.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing identifiers, controlling the amount orspecificity of data stored (e.g., collecting location data at city levelrather than at an address level), controlling how data is stored (e.g.,aggregating data across users), and/or other methods such asdifferential privacy.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, location dataand notifications can be delivered to users based on aggregatednon-personal information data or a bare minimum amount of personalinformation.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

1.-23. (canceled)
 24. A method comprising: at an electronic device incommunication with one or more wireless antenna, an output component,and one or more input devices: detecting a change in a location of aremote locator object relative to a location associated with a user; andin response to detecting the change in location of the remote locatorobject relative to the location associated with the user: in accordancewith a determination that the location associated with the user and thelocation of the remote locator object have been moving togetherrecently, and that first separation criteria are met, generating, viathe output component, a separation alert at the electronic devicewithout regard to whether second separation criteria have been met,wherein the second separation criteria are different from the firstseparation criteria; and in accordance with a determination that thelocation associated with the user and the location of the remote locatorobject have moved less than a threshold amount for at least a thresholdamount of time, and that the second separation criteria are met,generating, via the output component, a separation alert at theelectronic device without regard to whether the first separationcriteria have been met.
 25. The method of claim 24, wherein whether thefirst separation criteria have been met is based at least in part on asignal strength of the remote locator object as detected by theelectronic device, and whether the second separation criteria have beenmet is independent of the signal strength of the remote locator objectas detected by the electronic device.
 26. The method of claim 24,wherein whether the second separation criteria have been met is based atleast in part on whether the remote locator object or the electronicdevice have exited a geofenced region, and whether the first separationcriteria have been met is independent of the geofenced region.
 27. Themethod of claim 24, further comprising: after generating the separationalert associated with the remote locator object, detecting, via the oneor more input devices, input directed to the separation alert; and inresponse to detecting the input directed to the separation alert: inaccordance with a determination that the input corresponds to a requestto designate a current location of the remote locator object as atrusted location, initiating a process to designate the current locationof the remote locator object as a trusted location.
 28. The method ofclaim 24, further comprising: before generating the separation alert andbefore the electronic device is configured to generate separation alertsbased on separation of the remote locator object from the electronicdevice: detecting that the first separation criteria or the secondseparation criteria have been met; and in response to detecting that thefirst separation criteria or the second separation criteria have beenmet: in accordance with a determination that one or more criteria aresatisfied, including a criterion that is satisfied based on a number oftimes the first separation criteria or the second separation criteriahave been met, generating, via the output component, an indication thatthe electronic device can be configured to generate separation alertsbased on separation of the remote locator object from the electronicdevice.
 29. The method of claim 24, further comprising: whiledisplaying, via the output component, a user interface that includes arepresentation of a map: in accordance with a determination that a firstcomponent and a second component that are associated with each other arecurrently connected with each other, indicating, in the user interface,the first and second components with a first set of one or moreindications having a first visual appearance; and in accordance with adetermination that the first component and the second component that areassociated with each other are not currently connected with each other,indicating, in the user interface, the first and second components witha second set of one or more indications having a second visualappearance, different from the first visual appearance.
 30. The methodof claim 29, further comprising: in accordance with the determinationthat the first component and the second component that are associatedwith each other are not currently connected with each other: whiledisplaying, via the output component, a first indication correspondingto the first and second components, detecting, via the one or more inputdevices, an input directed to the first indication; and in response todetecting the input directed to the first indication, displaying, viathe output component, a second indication corresponding to the firstcomponent, and a third indication corresponding to the second component.31. The method of claim 29, further comprising: in accordance with thedetermination that the first component and the second component that areassociated with each other are not currently connected with each other:displaying, on the representation of the map: a first indicationcorresponding to the first component at a location on the representationof the map corresponding to a location of the first component, and asecond indication corresponding to the second component at a location onthe representation of the map corresponding to a location of the secondcomponent.
 32. The method of claim 29, further comprising: whiledisplaying, via the output component, a finding user interface,providing an option to switch between finding the first component andfinding the second component.
 33. The method of claim 24, wherein theseparation alert includes a representation of a map and a visualindication of the remote locator object displayed at a location on therepresentation of the map that corresponds to the location of the remotelocator object.
 34. The method of claim 24, wherein the separation alertincludes a selectable option that is selectable to display a userinterface associated with the remote locator object, wherein the userinterface associated with the remote locator object includes additionalinformation for locating the remote locator object.
 35. The method ofclaim 34, wherein the user interface associated with the remote locatorobject includes a visual indication that indicates a location at whichthe remote locator object was separated from the location of the user,and the visual indication is selectable to initiate a process todesignate the location at which the remote locator object was separatedfrom the location of the user as a trusted location for the remotelocator object.
 36. The method of claim 24, wherein: in accordance witha determination that one or more criteria are satisfied, the separationalert includes a selectable option that is selectable to initiate aprocess to designate the location of the remote locator object as atrusted location for the remote locator object.
 37. The method of claim36, wherein the process to designate the location of the remote locatorobject as a trusted location for the remote locator object includes: inaccordance with a determination that the remote locator object has beenseparated from the location of the user at the location of the remotelocator object without a respective set of one or more other remotelocator objects being separated from the location of the user at thelocation of the remote locator object, designating the location of theremote locator object as a trusted location for the remote locatorobject without designating the location of the remote locator object asa trusted location for other remote locator objects in the respectiveset of one or more other remote locator objects.
 38. The method of claim36, wherein the process to designate the location of the remote locatorobject as a trusted location for the remote locator object includes: inaccordance with a determination that the remote locator object and asecond remote locator object have been separated from the location ofthe user at the location of the remote locator object: designating thelocation of the remote locator object as a trusted location for theremote locator object; and designating the location of the remotelocator object as a trusted location for the second remote locatorobject.
 39. The method of claim 36, wherein designating the location ofthe remote locator object as a trusted location for the remote locatorobject does not designate the location of the remote locator object as atrusted location for one or more other remote locator objects that arenot separated from the location of the user.
 40. The method of claim 36,wherein: the one or more criteria include a criterion that is satisfiedwhen the separation alert was generated in accordance with thedetermination that the second separation criteria are met, and is notsatisfied when the separation alert was generated in accordance with thedetermination that the first separation criteria are met, and inaccordance with a determination that the one or more criteria are notsatisfied, the separation alert does not include the selectable optionthat is selectable to initiate the process to designate the location ofthe remote locator object as a trusted location for the remote locatorobject.
 41. The method of claim 24, wherein the separation alertincludes a selectable option that is selectable to initiate a process todisable separation alerts for the remote locator object.
 42. The methodof claim 24, wherein displaying the separation alert includes: inaccordance with a determination that one or more criteria are satisfied,wherein whether the one or more criteria are satisfied is based on anumber of times the remote locator object has been separated from thelocation of the user, displaying the separation alert concurrently withone or more options for adjusting separation alert settings for theremote locator object, and in accordance with a determination that theone or more criteria are not satisfied, displaying the separation alertwithout displaying the one or more options for adjusting the separationalert settings for the remote locator object.
 43. The method of claim24, further comprising: displaying, via the output component, a userinterface for designating one or more locations as trusted locations forthe remote locator object, wherein: in accordance with a determinationthat a respective location has been designated as a trusted location foranother remote locator object associated with the electronic device butnot the remote locator object, the user interface includes a selectableoption that is selectable to designate the respective location as atrusted location for the remote locator object, and in accordance with adetermination that the respective location has not been designated as atrusted location for another remote locator object associated with theelectronic device, the user interface does not include the selectableoption that is selectable to designate the respective location as atrusted location for the remote locator object.
 44. The method of claim43, wherein displaying the user interface for designating the one ormore locations as trusted locations for the remote locator objectincludes: in accordance with the determination that the respectivelocation has been designated as a trusted location for another remotelocator object associated with the electronic device but not the remotelocator object, displaying, in the user interface, a visual indicationof an identity of a second remote locator object for which therespective location has been designated as a trusted location.
 45. Themethod of claim 43, wherein displaying the user interface fordesignating the one or more locations as trusted locations for theremote locator object includes: in accordance with the determinationthat the respective location has been designated as a trusted locationfor another remote locator object associated with the electronic devicebut not the remote locator object, displaying, in the user interface, avisual indication of a number of other remote locator objects associatedwith the electronic device for which the respective location has beendesignated as a trusted location.
 46. The method of claim 24, whereinthe first separation criteria and the second separation criteria includea criterion that is satisfied when, prior to generating the separationalert, the location associated with the user and the location of theremote locator object exited a trusted location together, and is notsatisfied when, prior to generating the separation alert, the locationassociated with the user and the location of the remote locator objectdid not exit a trusted location together.
 47. The method of claim 24,wherein the first separation criteria and the second separation criteriainclude a criterion that is satisfied when at least one trusted locationhas been designated for the remote locator object, and is not satisfiedwhen at least one trusted location has not been designated for theremote locator object.
 48. An electronic device, comprising: one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: detecting a change in a location of a remote locator objectrelative to a location associated with a user; and in response todetecting the change in location of the remote locator object relativeto the location associated with the user: in accordance with adetermination that the location associated with the user and thelocation of the remote locator object have been moving togetherrecently, and that first separation criteria are met, generating, via anoutput component, a separation alert at the electronic device withoutregard to whether second separation criteria have been met, wherein thesecond separation criteria are different from the first separationcriteria; and in accordance with a determination that the locationassociated with the user and the location of the remote locator objecthave moved less than a threshold amount for at least a threshold amountof time, and that the second separation criteria are met, generating,via the output component, a separation alert at the electronic devicewithout regard to whether the first separation criteria have been met.49. A non-transitory computer readable storage medium storing one ormore programs, the one or more programs comprising instructions, whichwhen executed by one or more processors of an electronic device, causethe electronic device to perform a method comprising: detecting a changein a location of a remote locator object relative to a locationassociated with a user; and in response to detecting the change inlocation of the remote locator object relative to the locationassociated with the user: in accordance with a determination that thelocation associated with the user and the location of the remote locatorobject have been moving together recently, and that first separationcriteria are met, generating, via an output component, a separationalert at the electronic device without regard to whether secondseparation criteria have been met, wherein the second separationcriteria are different from the first separation criteria; and inaccordance with a determination that the location associated with theuser and the location of the remote locator object have moved less thana threshold amount for at least a threshold amount of time, and that thesecond separation criteria are met, generating, via the outputcomponent, a separation alert at the electronic device without regard towhether the first separation criteria have been met. 50.-112. (canceled)